Okay, I couldn’t resist. Since I’ve been speaking so often on the wonders of HTTP Streaming in AJAX applications.
Combine that with some slick inter-process communication, and AJAX for client->server data, and you have a very low-latency client-server interaction.
Here’s the issue, if you’re using PHP, one must remember that PHP waits until a script is completed before it echos data to the client. Not very helpful in a streaming environment. Therefore, it is necessary to use a flush() call after every instance of echo that you want to be sent to the browser in real-time. You can configure PHP to behave this way all the time, but it’s seriously sub-optimal and should basically be used only for debugging.
So there you have it, client->server with AJAX, server->client with COMET, and server< ->server with traditional UNIX IPC.