Thanks for the advice. I didn't know this project existed. I looked at the laszlo/red5 example (http://wiki.openlaszlo.org/RtmpRed5Webapp) and it looks very well integrated into laszlo in order to send and receive real time messages. Am I tied to using Flash 9+ with this method?
Since you brought red5 up, it's now a battle between a Laszlo/Red5/RTMP approach, and a Laszlo/Comet/Dojo approach. I know I would be able to use a Cometd approach, using Jetty and Dojo, but it seems like I would have to deploy the laszlo LPS to Jetty so that I could handle the Comet communication and laszlo compilation in one webapp. Here's a big question. Is it possible to deploy the red5/rtmp server to a different machine than the LPS and not run into cross browser communication issues? Say for example, that the LPS was running at http://localhost/lpsand red5/rtmp server was running at http://localhost:8080/rtmp. Would I be able to server up the lzx files from the LPS server and hit rtmp on a different server? I'll have to look into this red5/rtmp approach a bit more, but thanks. - Anthony Bargnesi On Jan 7, 2008 3:09 AM, Anze Cesar <[EMAIL PROTECTED]> wrote: > If you don't mind running another server and compiling to swf, you could > try running red5 and use rtmp. It's meant for audio/video streaming, but > it's not limited to that :). > > On 1/4/08, Anthony Bargnesi <[EMAIL PROTECTED]> wrote: > > > Hello Laszlo Users! > > > > Need help on alternative approaches to persistent connections! > > > > I am creating a tool that require every laszlo app instance to send > > events to each other much like a chat room. Naturally I gravitated to > > persistent connections, but I read everywhere that they are not fully > > supported in all browsers, and some browsers will behave differently. Since > > I want this laszlo application to run in all major browsers I think I better > > stay away from persistent connections. > > > > With that said, is there another "Tried and True" solution to this using > > the latest OL (4.0.7)? The alternative I was thinking of would be to > > use web services calls on the *back-end* server to send messages and > > then have each laszlo app instance poll the server for the latest messages. > > The problem I see with this is that polling the server unnecessarily will > > bog down the server and the polling isn't really real time...meaning laszlo > > app instances will incur some lag. > > > > Does anyone else have a solution that they used that has found to > > perform well when needing to send messages in real time to all laszlo app > > instances? Also, is the solution scalable for multiple "chatrooms" (so to > > speak)? > > > > Thanks very much, > > Anthony Bargnesi > > > > > > -- > lp, > Anže
