Filip Hanik - Dev Lists wrote:
I hear you loud and clear, I've addressed the bug in my previous email. In terms of breaking HTTP, the comet model already does this, as it would block the client from sending data until the server decides it is done sending data to the client, which it can do more than once.
No, the Comet model does not and must not break the HTTP protocol, it's simply that the whole request lasts a long time. Reading input is as arbitrary as it was before, and there must be some collaboration between the client and the server: if the client sends data that the server does not want to read (or consider), then the application isn't going to work.
I've attached the model that I am suggesting for Tomcat, as you can see, the only difference between the one I am suggesting and the comet model, is that the client also is enabled to send data more than once.
The client is obviously not limited to sending data once. Rémy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
