On Fri, Feb 27, 2009 at 1:08 PM, Hans Hübner <hans.huebner@gmail.com> wrote:

On Thu, Feb 26, 2009 at 22:01, Jim Prewett <download@hpc.unm.edu> wrote:

> I'm not quite sure what I'm after except that the buzzword seems to be
> "COMET".

...

The cleanest way to implement a high performance I/O multiplexing
framework that could be used by Hunchentoot would be by implementing
multiplexed socket streams using coroutines. Obviously, that would
require a coroutine library, and I am not aware of such a thing.

Don't you think that having separate thread handling comet would be simpler? I/O multiplexing to the clients with some sort of message queueing API for requests from the app engine would be sufficient to make it work? The only obstacle for multiplexed I/O is lack of portable non-blocking I/O library.

/S