hola community, after painful weeks working on a JMF-RTP based desktop sharing solution, it is now possible to test a basic version within current trunk.
to activate that solution, select it on install process or activate it via administration-> configration. i tested that on 3 different scenarios : red5 on localhost, red5 within intranet (clients and server within different subnets) and red5 in internet. -> the current version requieres a high bandwidth, so it isnt quite useful for internet working at the moment, even for intranet work it requires some optimizations. -> my benchmark for performance was to be able to see a fluid youtube video in high resolution from sharers desktop in intranet installation and that goal i reached for now.... (although that should not be the end of the research, just a milestone ;-)) heres a short description about the functionality of the sharer : 1. Moderator clicks "Share desktop button" -> download of a minimal (at the moment..) Java client 2. Moderator clicks "Start Sharing" within java client 3. Client starts recording desktop a streaming it as MJPEG to red5 servlet 4. Servlet sends notification to all conference members, that they can consume a desktop sharing session (small window within whiteboard) 5. Conference members can start Java applet via small window 6. After a view seconds, they see sharers desktop within Applet Known issues : - RTP Ports have a hardcoded spectrum at the moment, beginning at 22230 at the moment - Port Binding on Server : in some server configurations it is required to remove the loopback interface from /etc/hosts making the servlet possible to bind on local address, see sun forums for that topic - restarting RTP Session within same conference can cause troubles - at the moment, only conference members that are in room at point of starting desktop sharing can comsume stream) - RTP Port Administration on server side - performance : we still need to optimize the streaming :packet sizes, and even the sharers have to be configurable to debug, please activate java console on clients and check for red5 server log -> any testing results are welcome to get a better overview about differnet scenarions see ya Smoeker --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenMeetings developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/openmeetings-dev?hl=en -~----------~----~----~----~------~----~------~--~---
