 |
Search |
 |
|
|
Building GWT Comet based web app using Grizzly CometPosted by jfarcand on May 20, 2008 at 12:58 PM PDT
I'm getting a lot of requests to share our JavaOne BOF slides where we have demonstrated the use of GWT + Grizzly Comet. 
Download the presentation here. We are still working on cleaning up the demo (and make sure I can commit the GWT code inside the Grizzly workspace). So stay tuned for the demo, but it is so simple to use Grizzly Comet + GWT you might not even need a demo :-). Unlike Jetty, you don't need any changes to GWT core classes to make it work :-) I was thinking to start blogging about GWT + Grizzly Comet integration, but I still need to write the follow up to my Grizzly SIP implementation first, so the preso should be a good startup. If you have questions, post them here or send an email to users@grizzly.dev.java.net »
Related Topics >>
Java Enterprise Comments
Comments are listed in date ascending order (oldest first)
Submitted by jfarcand on Thu, 2008-05-29 14:05.
Hi Morock! Nice tutorial. I will link to it from grizzly.dev.java.net :-)!
Submitted by morock on Thu, 2008-05-29 14:25.
Thanks JF, me tutorial is still pretty rough, let me know if you have any tips. Also, let me know how your demo is going. I'd love to contribute!
Submitted by sboudrai on Thu, 2008-05-22 01:19.
Hi,
I would be deeply interested in your demo :)
I'm having some issues on the client side of GWT.
Sami
Submitted by morock on Wed, 2008-05-28 20:24.
I've written up a tutorial about how to do this here: http://www.javascriptr.com/2008/05/28/gwt-grizzly-comet/
Check it out, its pretty rough, I'll be making improvements to it in the following weeks.
Submitted by sboudrai on Fri, 2008-05-23 03:39.
The code I wrote for GWT using long connections works with Firefox but not with IE (or GWT hosted browser), even if I try to bypass the 256B internal buffer. I'm running on glassfish v2ur2.
I noticed the grizzly chat long connection doesn't work in IE either.
Submitted by jfarcand on Fri, 2008-05-23 08:14.
Hum, which IE are you using? Works fine for me on XP + IE 7. Can you also point me to the proper example you have used? Better, can we continue the discussion on users@grizzly.dev.java.net. Thanks!!!
Submitted by bertung on Thu, 2008-05-22 06:35.
how would you ensure scalability over long lived connections at server side, especially if we have only one entry point to a server farm? It basically sounds more like an application, made only for a single physical server.
Submitted by jfarcand on Thu, 2008-05-22 08:17.
Berlung, if you are planning to use Comet (GWT is not important here) inside a farm, you will need to make sure all the server inside the farm can communicate between them. With GlassFish, you usually uses JMS between Server to share the information. So if a request is sent to server-1, server-1 will send, via JMS, the request info to server-2, so both server-1 and server-2 can initiate a server push to their respective long lived connection. -- Jeanfrancois
Submitted by marcoflower on Sun, 2009-01-11 02:43.
Hi JF! I'm developing a GWT application using GWT-RPC and Grizzly. My application works fine using Long Poll connections but I'd like to notify the client using the Streaming mode. I tried to remove context.resumeCometHandler() but the GWT-RPC doesn't receive the notification... Can you help me? Thanks.
Submitted by jfarcand on Mon, 2009-01-12 09:59.
See the answer here: http://tinyurl.com/axyj82 and the following discussion.
|
|
|
||
|
