David Delbecq schrieb:
Here a diagram:
Client sends GET -> Server
Server sends HEADERS (Content Encoding: Chunked) -> Client
Server sends chunks -> Client
Client displays them whenever they arrive.
Just one point. If your 'client' is a classical browser it won't work
like this out of the box,
Remy Maucherat schrieb:
On 4/3/06, Tp <[EMAIL PROTECTED]> wrote:
Remy Maucherat schrieb:
But you said that the connection will not close, when the doGet() or
doPost() method returns, which of course make a lot of sense. Otherwise
Persistent connections would not be possible at all.
Remy Maucherat schrieb:
On 4/3/06, Tp <[EMAIL PROTECTED]> wrote:
Well, I don't know what you understand under polling. I guess you mean
the clients will have to sent GET and POST requests repeately, right?
The load is going to be even higher with polling. That's I would n
Leon Rosenberg schrieb:
On 4/3/06, Rajeev Jha <[EMAIL PROTECTED]> wrote:
Remy Maucherat wrote:
Yes, but you need the 5000 or so threads to do this, and there's no
workaround. So it is the real problem since it forces you to use
polling.
How about bypassing the servlets alltogether?
we
Rajeev Jha schrieb:
Remy Maucherat wrote:
Yes, but you need the 5000 or so threads to do this, and there's no
workaround. So it is the real problem since it forces you to use
polling.
How about bypassing the servlets alltogether?
we can take any exisitng http/ajp13 connector code and rep
Remy Maucherat schrieb:
On 4/3/06, Tp <[EMAIL PROTECTED]> wrote:
The hype friendly "continuation" name has no business being associated
with this particular feature, since the said feature is not
continuations (which is a fancy - and IMO forward thinking and
actually useful - p
David Delbecq schrieb:
Tp a écrit :
Hi,
we have to develop a high performance chat based only on HTML and HTTP
only for a television company. The chat's output window requires one
open HTTP connection per client, which means that you need at least
3000 simultaneous ie. open HTTP connec
Remy Maucherat schrieb:
On 4/3/06, Rajeev Jha <[EMAIL PROTECTED]> wrote:
Tp wrote:
And there seems to be no workaround, because the connection will close
after the doGet() and doPost() method finishes (is that actually
true?). So, the only way to keep 3000 simultaneous connections is t
Rajeev Jha schrieb:
Tp wrote:
And there seems to be no workaround, because the connection will close
after the doGet() and doPost() method finishes (is that actually
true?). So, the only way to keep 3000 simultaneous connections is to
keep 3000 of those methods from returning, wehich
Hi,
we have to develop a high performance chat based only on HTML and HTTP
only for a television company. The chat's output window requires one
open HTTP connection per client, which means that you need at least 3000
simultaneous ie. open HTTP connections for 3000 chatters.
To the former pos
Remy Maucherat schrieb:
On 4/3/06, Tp <[EMAIL PROTECTED]> wrote:
Hi,
we have to develop a high performance chat based only on HTML and HTTP
only for a television company. The biggest issue is performance. The
chat's output window requires one open HTTP connection per client. This
Hi,
we have to develop a high performance chat based only on HTML and HTTP
only for a television company. The biggest issue is performance. The
chat's output window requires one open HTTP connection per client. This
means, that when you have 3000 people following the chat that the server
has
12 matches
Mail list logo
