Hi Dave
I see two situations where this can be a problem (particularly when
related to file serving) which would need a lot of extra code to work
properly.
1. Large files. Using the "seek" command would get around this.
2. Dynamic environments where file contents can change.
So serving ever-changing large files would need a few locks & checks.
I haven't tried this but if you use the for write form to open a file
for writing does this mean the same file cannot be opened for a read?
regards
alex
Dave Cragg wrote:
This would put an extra burden on the scheduler when it has to write
back large quantities of data to simulataneous requests from different
clients. But I think it should be possible to slice up the responses so
that you only write back to the client sockets in small chunks (say 4096
KB at a time). This should allow simultaneous connections to appear to
work simultaneously.
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
