[Info-vax] CRTL and RMS vs SSIO

[Craig A. Berry]

On 10/7/21 8:40 AM, Arne Vajhøj wrote:
> On 10/7/2021 8:50 AM, Craig A. Berry wrote:
>> On 10/6/21 11:10 PM, Dave Froble wrote:
>>> the real issue is that SSIO was aimed (it seems) at PostgreSQL.
>>
>> And Apache, and Samba, and other things that have been explicitly
>> mentioned as having needed app-specific workarounds due to the absence
>> of shared stream I/O support. SSIO *is* the general-purpose solution
>> that you seem to be lamenting the lack of.
> 
> Samba I totally get.
> 
> Multiple PC's writing to a file on a Samba share would create
> some interesting scenarios.
> 
> But why does Apache need it?
> 
> It should read files to serve - and since it is serving VMS files
> then I think it be as VMSish as possible so totally standard RMS.
> And it should write sequential text files like access.log.
> 
> What am I missing?

log files (and probably the fact that multiple worker processes can be
writing to the same logs).  And I forgot to mention that Java needs it
too.  See:

<http://de.openvms.org/TUD2012/opensource_and_unix_portability.pdf>

Page 16 says:

• Java (CIFS too) uses a work-around
   − Does open+read/write+close for every read/write!
   − Restores current file offset after each close+open
   − Significant performance issue
• Oracle problem with log and trace files
   − Single writer with multiple readers
• Apache’s use of log files sub-optimal
   − V1.3 places restriction
   − V2.0 uses a work-around