Thanks Brian - I've done this way back in the past using php. It worked, but I wanted to avoid 2 things... 1) constantly hitting the server to look for new data, and 2) the app feeling slow. With the example mentioned in my first post the app feels very very snappy.
Aside from that, does anyone know/think that I should be looking into something involving "event gateways" instead? Thanks, John On Jun 8, 2007, at 8:12 AM, Brian Swartzfager wrote: > I once built a chat room tool using CF and AJAX so my wife (a high- > school teacher) could use it to hold scheduled chat sessions with > her students who had study/assignment questions. I simply had the > JavaScript on the client-side make a request to the server for any > new messages every few seconds (each request would pass in the > unique ID number of the last chat message displayed to the user, > and the request would return any messages with a higher message ID > number). > > It seems to me it's a lot less work for the server if the client > takes responsibility for looking for new content, but it may depend > on the context of how the chat tool will be used: single chat > rooms with multiple participants, where the conversation is fast, > or numerous one-on-one chats where there may be long pauses between > new posts. > > --Brian > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Deploy Web Applications Quickly across the enterprise with ColdFusion MX7 & Flex 2 Free Trial http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJU Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:280469 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
