🚀 go-pugleaf

In article <STEINARB.91May4124947@fenris.idt.unit.no>, steinarb@idt.unit.no (Steinar Bang) writes:
|> I saw some comments to the effect that C++ streams are out as a basis for
|> InterViews RPC (or rather: will be removed when time permits).
|> Instead memory mapped files will be used on the systems that implements
|> them.
|> 
|> I can see that this is more efficient than using streams. Two things that
|> bother me, however:
|>  - Not all systems will implement memorymapped files.
|>  - Net transparancy will be lost.
|> 
|> Will you continue to support RPC classes that uses streams (maybe based on
|> ANSI C <stdlib> function calls)?

My comment was in reference to file i/o, not rpc.  The idea is to have a File class
that hides allows mmap to be used; it could also support normal read/write.
I don't expect this to have any impact on rpcstreams.