Status on entering July

14 views
Skip to first unread message

John Roy

unread,
Jul 4, 2013, 10:02:19 PM7/4/13
to babe...@googlegroups.com
June
----

* Completed server release and associated documentation: https://groups.google.com/d/msg/babelroom/m5DzKGIV7ds/zqGLQeJoSOMJ

* Completed research and development on WebRTC and rolled our test room here: http://test.babelroom.com/webrtc -- very interesting. As many have noted this technology is poised to revolutionize -- but it's still quite bleeding edge. FreeSWITCH announced an important milestone for support of WebRTC: http://www.freeswitch.org/node/455

* Along with the WebRTC development video signalling was completely rewritten. This logic signals indicators for video related events such as when webcams become available or offline, video and audio stream available or paused etc. etc.  

* The WebRTC effort also introduced "peer-to-peer" conferences as an alternative to centralized audio. This model always a modest investment in servers to scale reliably to high volumes - it may prove interesting for economical deployment of large numbers of basic conferences with a very small number of attendees. By large numbers we mean millions.

* Started research on mobile development -- specifically looked at the SIPdroid client and how it may be customized to provide an android SIP client http://sipdroid.org/ . For those who are unaware, babelroom supports direct audio access into conference rooms via SIP, simply use <your pin code>@sip.babelroom.com as target address -- specific instructions will vary depending on your SIP client. Install a SIP client (SIPdroid, Linphone, SIPhon etc.) on your desktop or mobile then connect with much higher quality audio than telephone and no telephone charges. 

July and Beyond
----

* Merge the WebRTC related developments noted above into the main production release.

* Some documentation / feedback and a review of bugs is needed.

* There's been several requests/ideas from the elgg community and since engagement has been comparatively high there a new release is perhaps due.

* There has to be a much better way to generate API documentation -- investigating this tool: http://apiary.io/ 
Reply all
Reply to author
Forward
0 new messages