To repeat Dossy: wow, they came with a cool new name for something old! :) That said: in principle, AOLserver is perfectly able to do this as it has the ability to just keep the connection open for as long as you like and stream the data. You should be thinking of a registered proc or .tcl file using ns_write.
But... Every connection would take up a thread, even if it is idle. Having 1000 simultanious users might be a bit of an issue for any standard web server. Say you have a chatroom application. In an ideal world you would be using non-blocking IO for this; all the clients are connected and a list of all the connections subscribed to the chat channel is kept. Someone posts (using AJAX) to the channel and the handling thread simply steps through all the connections and sends the message to each client. An architecture like that would scale very well, but AOLserver couldn't do it out of the box. I am not sure how much effort it would be the write it. You are probably looking at writing a module that does all of it and exposes some Tcl commands to send messages to clients. Hope that helps! Bas. Hamilton Chua said: > I read a recent article about something that could be the next buzz word > after > Ajax and Mashups. > > http://www.irishdev.com/NewsArticle.aspx?id=2166 > > What I would like to find out more about what the article is talking about > "event driven IO" in the context of AOLServer. > > Does anyone know of a module in aolserver that supports this or are there > currently plans to build this "abstraction". > > Thanks ! > > > -- > AOLserver - http://www.aolserver.com/ > > To Remove yourself from this list, simply send an email to > <[EMAIL PROTECTED]> with the > body of "SIGNOFF AOLSERVER" in the email message. You can leave the > Subject: field of your email blank. > -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
