I see. Has the streaming logic been improved much since .5 final ? Also... the major issue right now that's a roadblock in my project is disconnection. Sometimes the app disconnect methods aren't called when the client has disconnected from the server. This bug exists from ver 4.1 to trunk.
I'm developing a webcam videoconference with no voice. Version .5's streaming is buggy & a bit slower. Version .41's streaming works fine for me, except for this disconnection issue. I've tried workarounds, such as adding a Java timer that pings the clients to make sure theyre alive.. but learned that spawning a thread for the timer causes red5 to break.
Then, I noticed ver .5 introduced a task method for calling tasks periodically... so assumed you guys knew about this issue. Which would have been just what I needed to implement ping if ver .5 weren't buggy.
Any ideas?
I'm developing a webcam videoconference with no voice. Version .5's streaming is buggy & a bit slower. Version .41's streaming works fine for me, except for this disconnection issue. I've tried workarounds, such as adding a Java timer that pings the clients to make sure theyre alive.. but learned that spawning a thread for the timer causes red5 to break.
Then, I noticed ver .5 introduced a task method for calling tasks periodically... so assumed you guys knew about this issue. Which would have been just what I needed to implement ping if ver .5 weren't buggy.
Any ideas?
-----Original Message-----
From: [EMAIL PROTECTED]
To: [email protected]
Sent: Fri, 1 Sep 2006 9:48 AM
Subject: Re: [Red5] which OS is recommended to run Red5 ?
On Fri, 2006-09-01 at 10:42 -0400, [EMAIL PROTECTED] wrote: > Yes, that's Sun's mantra.. write once, run anywhere.. but anyone who > has been coding Java since day one knows it's a lie. Java compiles > and runs on every os with an equivalent jvm version... but doesn't > always run precisely the same way. Issues can surface at the os level > ie. jvm compatibility/availability, drivers, etc. > > It's still possible to write code that compiles and runs differently > on another platform.
I've never heard of OS dependent problems with red5. All the bugs we have are in streaming logic. It's not a question of JVM behaviour. -- Michael 'Antares' Klishin novemberain.com | flexwiki.novemberain.com | osflash.org/red5 | rubyonrails.ru _______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
_______________________________________________ Red5 mailing list [email protected] http://osflash.org/mailman/listinfo/red5_osflash.org
