search

phamtuanchip / gwt-comet

Automatically exported from code.google.com/p/gwt-comet
0 stars 0 forks source link

Connection response time #17

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Create a comet connection.
2. Print out the time just before calling the "CometSession.enqueue" method on 
the server.
3. Print out the time when the message is received on the client in the 
"onMessage" method.
4. Do the same thing, this time without comet.  Just use the regular GWT RPC 
client-server calls.

What is the expected output? What do you see instead?
Comet response time is greater than the RPC call.  Expected (hoped?) it would 
be quicker to use comet.

What version of the product are you using? On what operating system?
gwt-comet-1.2.1
Ubuntu
Firefox 3.6

Please provide any additional information below.
Maybe there are some configurations I can override, but should I expect the 
Comet response time to be greater than just polling and using RPC?  With a 
short poll interval, it is quicker than using Comet.

As an example of my measurements, the RPC call took 250ms to respond from 
server to client, and the Comet call took 450ms.

Original issue reported on code.google.com by sdcma...@gmail.com on 2 Mar 2011 at 7:03