I have created a Stratus Multicast whiteboard as well as a LCCS/Stratus P2P hybrid. On http://www.colabry.com the top whiteboard remains the LCCS whiteboard and the lower is the Stratus P2P. The Stratus P2P now includes LCCS connectivity.
You are invited to see the Multicast whiteboard by sending me an email: ajlogo@gmail.com . This version as well as both earlier mentioned whiteboards are virtually all the same code. I see two huge advantages to Stratus multicast:
1. More engaging due to free/un-metered use. Using LCCS to broadcast slider adjustments, window resizing, mouse and window scroll bar movements are potentially expensive. It is easy to imagine 36,000 messages a hour.
2. Whiteboard over simple P2P ( two people max) is minamally collaborative.
The down side is that roles/rooms/credentials and other LCCS comforts need to be created. And the base content needs to be persistent somewhere.
I want to reiterate my suggestion to watch the talk by Matthew Kaufman at 2009 MAX (esp at ~ 39:00)
http://tv.adobe.com/watch/max-2009-develop/p2p-on-the-flash-platform-with-rtmfp
Arnie
ajlogo@gmail.com
February 2, 2010 at 6:59 am |
Dear Ajlogo
I find that you are the expert in the adobe p2p tech. i learn much from you. i find you recently finich a program “Whiteboard over
simple P2P( two people max) is minamally collaborative”. in the link”http://forums.adobe.com/thread/553827″
I am now working on a project about p2p tech, and need a simple P2P Whiteboard source code to help me, my email is qingyun.li@gmail.com
Could you please send me the sourcecode of the “simple P2P Whiteboard”? it is just for education not for business.
Regards
liqingyun
February 2, 2010 at 1:42 pm |
Qingyun Li,
Thank you for the kind words. I can not supply source code, but can outline the important items.
1. Create an interpreter which can be called directly or by a chat message. This is the most important item. The interpreter can be very simple to start with:
if(chatMessage ==”newWBPanel”) createWBPanel();
else if(chatMessage==”sizePanel”) sizePanel(200,200);
by adding a tokenizer/parser more complex express can be interpreted.
2. When handling events, send messages to the interpreter to execute. The message are also sent (by chat) to the other interpreters to execute.
3. Create objects by the interpreter such as Panels, Canvases, Buttons etc. which are serializable; meaning the current state can be read in a manner that the state can be recreated by the/another interpreter.
March 13, 2011 at 11:18 am |
yes, Of course, what a critical orientation and communicative post.