Peter Warren wrote:
Hmm, ok. Sending the headers up causes the comet servlet to behave as I
expected, one BEGIN event generated on the first client request and one
READ event generated on the second request. In my simple test, the
comet servlet doesn't receive the headers as data. If I don't s
Hmm, ok. Sending the headers up causes the comet servlet to behave as I
expected, one BEGIN event generated on the first client request and one
READ event generated on the second request. In my simple test, the
comet servlet doesn't receive the headers as data. If I don't send up
the headers on
you're treading dangerous waters my friend. the comet is somewhat like a
real socket, and sending up new HTTP headers might end up just being
data for the Comet servlet.
Filip
Peter Warren wrote:
My client code was the problem. I had been thinking of the comet
interaction with the server as
My client code was the problem. I had been thinking of the comet
interaction with the server as similar to a socket, open it once and
then read and write merrily from either end. I forgot that comet is
still operating over http and the client needs to send http headers for
each request. So the f
