Comments on: GTUG Campout Follow up http://www.shaunabram.com/gtug-campout-followup/ Java and Technology weblog Thu, 02 Sep 2010 07:14:08 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Matt G http://www.shaunabram.com/gtug-campout-followup/comment-page-1/#comment-8434 Matt G Mon, 10 Aug 2009 18:16:36 +0000 http://www.shaunabram.com/?p=510#comment-8434 Very nice. An ambitious project for a weekend! Impressive to see how much you were able to get accomplished. Very nice. An ambitious project for a weekend! Impressive to see how much you were able to get accomplished.

]]> By: admin http://www.shaunabram.com/gtug-campout-followup/comment-page-1/#comment-8431 admin Mon, 10 Aug 2009 17:23:51 +0000 http://www.shaunabram.com/?p=510#comment-8431 Hey Vishal, Thanks for posting. Yeah, I think the demo problems were caused by the browser on the demo laptop having problems with JavaScript. Another group seemed to have similar problems with the same laptop. It was unfortunate as our app seemed to be working fine and updating correctly. Oh well, technical demos are prone to such problems! As for open sourcing, yes that is something we may investigate. Much of what we utilized is already open sourced (including the Federated Wave prototype server and the TiddlyWiki client). But I think, in particular, there may be some benefit in us releasing our code that deals with the Wave client/server communication. There is no standard way of implementing the Wave client/server communication protocol, so providing our communication layer that takes care of that is an option. It is based on the same approach used in the (also already open sourced) console based Wave client, but in a more accessible form. We essentially created a client (actually, servlet) side stub to facilitate the communications and allow our Wiki to make and receive updates to the Wave. I also know that Sriram (who started the team) has lots of ideas on extending the Wiki and client parts too. Update: Interestingly, Sriram pointed me to this (http://groups.google.com/group/wave-protocol/browse_thread/thread/fbfd74796e11fa17?hl=en) discussion where some folks have the same idea as us about client/server comms! Hey Vishal,
Thanks for posting. Yeah, I think the demo problems were caused by the browser on the demo laptop having problems with JavaScript. Another group seemed to have similar problems with the same laptop. It was unfortunate as our app seemed to be working fine and updating correctly. Oh well, technical demos are prone to such problems!

As for open sourcing, yes that is something we may investigate. Much of what we utilized is already open sourced (including the Federated Wave prototype server and the TiddlyWiki client). But I think, in particular, there may be some benefit in us releasing our code that deals with the Wave client/server communication. There is no standard way of implementing the Wave client/server communication protocol, so providing our communication layer that takes care of that is an option. It is based on the same approach used in the (also already open sourced) console based Wave client, but in a more accessible form. We essentially created a client (actually, servlet) side stub to facilitate the communications and allow our Wiki to make and receive updates to the Wave.

I also know that Sriram (who started the team) has lots of ideas on extending the Wiki and client parts too.

Update: Interestingly, Sriram pointed me to this (http://groups.google.com/group/wave-protocol/browse_thread/thread/fbfd74796e11fa17?hl=en) discussion where some folks have the same idea as us about client/server comms!

]]> By: Vishal http://www.shaunabram.com/gtug-campout-followup/comment-page-1/#comment-8422 Vishal Mon, 10 Aug 2009 07:13:40 +0000 http://www.shaunabram.com/?p=510#comment-8422 Shaun, I thought you & team did an excellent job. Sorry,that demo not work out.Would love to see your work. Are you planning to open source the code? thanks vishal Shaun,

I thought you & team did an excellent job. Sorry,that demo not work out.Would love to see your work. Are you planning to open source the code?

thanks
vishal

]]>