[Info-vax] Re; Spiralog, RMS Journaling (was Re: FREESPADRIFT)

[Phillip Helbig undress to reply]

In article <nkis8e$dk8$1 at news.albasani.net>, Jan-Erik Soderholm
<jan-erik.soderholm at telia.com> writes: 

> > But, to get serious for a moment, (yes, I can do that now and then), in
> > practice perhaps it's not such a big issue.  For example, I'm not
> > everybody, but, I do not send large pieces of data.  I've never sent
> > anything that could not easily be read into memory prior to transmission.
> > Got to ask, in general, how often is rather large text files transmitted to
> > / from a web server?
> 
> Any fairly modern web page can have 100s of different objects. Large text
> files might not be that common, but there are usualy a lot of images
> for buttons, icons and general page contents.

Right.  I recently downloaded a 4-GB PDF file.  Yes, on some machines it 
will fit into memory.  :-|

> If we look at WASD that I know about, it maintaines an internal file-cache
> where both the HTTP headers (which includes the byte-size) and the actual
> content is saved in a format that is fast to retrive and send. So instead
> of opening the soure file, a cached copy is used.

Same with OSU.  One can also run OSU on a no-cache port (I use this 
mostly for development, where I want to be sure I see the latest version 
of a recently changed page).