On 17 Nov 2009, at 16:49, Tom Schindl wrote:
> What you describe here is called Continuations in Java world :-)
Continuations in the Java world are the same as continuations everywhere - but
not quite what the OP described :)
http://en.wikipedia.org/wiki/Comet_(programming)
--
Andy Armstrong,
Nicolas George schrieb:
> Hi.
>
> There is an increasingly popular technique to emulate server-initiated push
> over HTTP. I'm sure everyone here knows it well, but for the sake of
> completeness: the clients sends a XMLHttpRequest to the server in the
> background; the server does not answer it i
On Fri, Nov 13, 2009 at 1:19 AM, Scott Gifford
>
> This is a very interesting idea, it might be possible to implement it
> with a custom Apache module, or maybe even with mod_perl if you found
> the right hooks.
>
> Scott.
so we're talking about a mod_perl app that opens a file system socket
Nicolas George writes:
> Hi.
>
> There is an increasingly popular technique to emulate server-initiated push
> over HTTP. I'm sure everyone here knows it well, but for the sake of
> completeness: the clients sends a XMLHttpRequest to the server in the
> background; the server does not answer it i
Le duodi 22 brumaire, an CCXVIII, Perrin Harkins a écrit :
> That's good enough for most applications, and the "nothing to see
> here" requests can be handled very quickly.
For what I have in mind, the actual content is rather small so the overhead
of the empty requests is huge.
> If you really n
[ I think ezmlm has eaten my mail. Sorry if it arrives twice. ]
Le duodi 22 brumaire, an CCXVIII, Michael Peters a écrit :
> I wouldn't write your own. There are other event based, asynchronous web
> servers out there in Perl (HTTP::Server::Multiplex, Net::Server::Coro,
> Tatsumaki) so better
On Thu, Nov 12, 2009 at 3:33 PM, Nicolas George
wrote:
> I will definitely not use polling, because polling means dozen of useless
> requests and, when there is actually something, it has to wait to the next
> round of polling.
That's good enough for most applications, and the "nothing to see
her
Le jeudi 12 novembre 2009 21:33:48, Nicolas George a écrit :
> he fact that HTTP is not connection-oriented
> means that the server have to implement cookies and timeouts itself to
> track clients instead of relying on the OS TCP stack, but that is not very
> hard.
Just to clarify your meaning,
On 11/12/2009 03:33 PM, Nicolas George wrote:
If I can not do it with Apache and mod_perl, I will write my own HTTP
server. But that is a shame, because it has to serve static content too, and
that, Apache does definitely better than me.
I wouldn't write your own. There are other event based,
Hi.
Le duodi 22 brumaire, an CCXVIII, Joel Richard a écrit :
> I may be off base, but I think this technique would be ineffective since
> the server process would be kept busy with an open connection to the
> browser. Eventually you'll run out of processes what with all the
> clients that end
On Thu, Nov 12, 2009 at 1:53 PM, Nicolas George
wrote:
> There is an increasingly popular technique to emulate server-initiated push
> over HTTP. I'm sure everyone here knows it well, but for the sake of
> completeness: the clients sends a XMLHttpRequest to the server in the
> background; the serv
I may be off base, but I think this technique would be ineffective
since the server process would be kept busy with an open connection to
the browser. Eventually you'll run out of processes what with all the
clients that end up waiting for something to happen. HTTP is a pull
protocol. :)
Hi.
There is an increasingly popular technique to emulate server-initiated push
over HTTP. I'm sure everyone here knows it well, but for the sake of
completeness: the clients sends a XMLHttpRequest to the server in the
background; the server does not answer it immediately, but keeps it for
later w
13 matches
Mail list logo
