On 29/04/07, Sam Lawrance <[EMAIL PROTECTED]> wrote:
> 2. Depending on the server's side, this particular program could > get into a > deadlock since it relays on the server having large enough buffers > to send > files and receive requests before the client finishes sending all > the file > names (even though he's careful to switch to non-blocking mode when > sending > requests - he still doesn't clear up the downstream buffer). Can you explain (2) a bit? I don't understand the deadlock condtions.
Actually, thinking about it again - the non-blocking write on the client will avoid this - it just means that the client might not send all the requests it wants before having to go to the next stage to start retrieving the responses. Sorry for the confusion. --Amos -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
