Ah, neat, I'll try it. We use this kind of polling at work between a flex client and a tomcat server with blazeds. Blazeds calls it long polling. One thing to look out for is the increase in memory and stuck processing threads caused by many open connections. Blazeds limits the number of long polling connections you can have at a time to a default of 100, configurable and recomends a max of 200, after this number all coming requests are treated as normal polling.
mihai On Wed, 5 May 2010 20:52:37 +0200 Tommi Mäkitalo <[email protected]> wrote: > Hi, > > great to hear, you tried tntnet and also tntdb. > > We currently play with reverse ajax using tntnet. I would like to > rewrite the chat application using this pattern. It reduces the > server load and also the latency. > > The idea is, that the chat client request the next message, but the > server waits some time, if a new message arrives. When the server > sends the reply, the client sends the next request immediately. So > when really a message arrives, the server can quickly send the > message to the client. > > There is also a demo application in tntnet called rajax-jquery. As > the name suggests, it also shows, how to use jquery with tntnet. > > The demo is not yet in the stable tntnet but can be found in svn. > > > Tommi > > ------------------------------------------------------------------------------ > _______________________________________________ > Tntnet-general mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/tntnet-general ------------------------------------------------------------------------------ _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
