Arnab Ganguly <[EMAIL PROTECTED]> wrote: >> Thanks for help and giving me a wonderful example.Can you give me >> some more inputs littile bit off topic, suppose some user is >> downloading the file, once the download is complete then only the >> final 200 ok is propagated to the client from the server or there >> would be in between message interaction with the client as well?
For a straightforward HTTP download, there would usually only be a single entry in the log file, with a 200 status code. But there are circumstances, most notably PDF files, where, if the server supports it, you may encounter partial downloads, with repeated 206 status codes. (http://analog.cx/docs/faq.html#faq143) >> Also where does the Client ,Server message transaction timer comes >> into the picture as in this case it takes long time for downloading >> so the timer is going to expires. That's really more of a server specific question - different servers could deal with it in different ways. But strictly speaking a time-out doesn't occur, because there is continuous communication between the client and server during that download - the server only sends packets as the client requests them, otherwise the server, with it's high speed connection, would just spit out the whole transaction faster than the client could accept it. Aengus +------------------------------------------------------------------------ | TO UNSUBSCRIBE from this list: | http://lists.meer.net/mailman/listinfo/analog-help | | Analog Documentation: http://analog.cx/docs/Readme.html | List archives: http://www.analog.cx/docs/mailing.html#listarchives | Usenet version: news://news.gmane.org/gmane.comp.web.analog.general +------------------------------------------------------------------------
