Thursday, March 29th, 2007
OpenAjax Hub: DWR, TIBCO, Lightstreamer example
<>p>Joe Walker has discussed the progress of the OpenAjax Hub. He has participated in a demo of using the OpenAjax Hub with DWR or Lightstreamer. TIBCO GI is the UI side, and it plugs into either backends with no code changes.With a traditional request/response model, DWR (and Lightstreamer) would be calling GI routines to update. With the pub/sub model the distinction between client and server is gone because the UI publishes things it’s interested in back to the hub. There’s no reason the UI has to be GI even: any UI that groks the OpenAjax hub can play. We could even have several UI components listening to the same messages on one page.
The OpenAjax Hub is getting close to a 1.0 release, and I’m hoping that DWR will have a server-side version of the OpenAjax hub soon after. This would allow you to transparently co-ordinate remote hubs, and even allow publishing of messages from one browser to another.
I’ve put the DWR version live so anyone can have a play. It’s not exciting, but you can see it in action. Just click on an “Industry Sector” to see messages published to that sector. See the DWR/OpenAjax/GI demo. I hope to move where it is hosted soon, and this is definitely something of a test, so don’t be surprised if you get a 404. I hope we can get a demo of the Lightstreamer version live soon too.
Related Content:
I nearly put into the blog post: “This is just a test, please don’t link to it Dion” ;-)
To see data streamed from the server, click on an industry sector. As I said in the blog post, It’s not pretty – the point is the integration.
It seems to be handling the load ok so far. Just in case it breaks – for high load I would probably configure tomcat and DWR to handle more threads then they do by default.
If you see pauses in the stream, it’s because Tomcat or DWR is slowing things down to avoid breaking the server.
Sort functionality seems to be broken on columns other than ID column. Overall too slow to initiate for what it is doing. I don’t see the point of popping that splash screen on each reload when scripts are already loaded, I personally wouldn’t slap any sort of “powered by me” into my customers face, odd place for it to be in the middle of the page
To see data streamed from the server, click on an industry sector. As I said in the blog post, It’s not pretty – the point is the integration.
It seems to be handling the load ok so far. Just in case it breaks – for high load I would probably configure tomcat and DWR to handle more threads then they do by default.
anyway,Thank u for your sharing
It seems to be handling the load ok so far. Just in case it breaks – for high load I would probably configure tomcat and DWR to handle more threads then they do by default.