On 2004.08.19, Wojciech Kocjan <[EMAIL PROTECTED]> wrote: > For returning files, you can always work the way [fcopy] does - leave > the fp open and when the socket is writable, read some more and send it. > > This wouldn't be too resource consuming. I've never seen too many HTML > files above 100K (20s on a 57k6 modem anyone? :), usually the largest > ones are static files. On average, my dynamic HTML code is usually > 20-30K at most.
Think: WebDAV. It's a real possibility that folks will upload and/or download files that exceed 10MB. > The problem could be with people storing files as BLOBs, but then again > they have to be read into memory and sent back to the client now as > well... So this doesn't change much. On Linux at least, use of sendfile() could be a win as the data doesn't have to go through userland before it gets shoveled out the socket back to the client. Probably not worth using given the many limitations on sendfile() though ... -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
