Details
-
Type:
Bug
-
Status:
Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 6.1.0rc0
-
Component/s: Continuations
-
Labels:None
-
Number of attachments :
Description
According to http://groups.google.com/group/cometd-dev/browse_thread/thread/4d6c2bdaa0c68901/719571116a7aebb2#719571116a7aebb2
the response to /meta/connect should return immediately to the client as the connectionId is included there.
Currently the cometd implementation waits for new messages to arrive before returning an answer (using a long-polling transport). I think the solution is as simple as setting the transport.setPolling to false in the ConnectHandler.
fixed.
thanks