Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
Right now I'm not hot about reading the data first in the container:
if done, it should be in InputBuffer,
yes, that is how I suggested it to be done. The AprBuffer was reading
the socket data in my checkin.
but could mean automagically di
Filip Hanik - Dev Lists wrote:
Right now I'm not hot about reading the data first in the container:
if done, it should be in InputBuffer,
yes, that is how I suggested it to be done. The AprBuffer was reading
the socket data in my checkin.
but could mean automagically discarding data, which co
Remy Maucherat wrote:
Filip Hanik - Dev Lists wrote:
I agree, chunked would be the way to go for a communication.
I reverted my fix, however, now TC6 has a DOS possibility, by
following these steps
1. Override CometServlet.read, always return true (you wanna serve N
client requests, and you
Filip Hanik - Dev Lists wrote:
I agree, chunked would be the way to go for a communication.
I reverted my fix, however, now TC6 has a DOS possibility, by following
these steps
1. Override CometServlet.read, always return true (you wanna serve N
client requests, and you don't know how many it
I agree, chunked would be the way to go for a communication.
I reverted my fix, however, now TC6 has a DOS possibility, by following
these steps
1. Override CometServlet.read, always return true (you wanna serve N
client requests, and you don't know how many its gonna send, so this is
not un
