CometSession not serializable

[GoogleCodeExporter]

What steps will reproduce the problem?
1. put <distributable/> on your web.xml file, at Chat example
2. try to login
3. the server generates an exception

What is the expected output? What do you see instead?
Expected: login
Got: setAttribute: Non-serializable attribute with name 
net.zschech.gwt.comet.server.CometSession
at line:
CometSession cometSession = CometServlet.getCometSession(httpSession);

What version of the product are you using? On what operating system?
1.1.3, Glassfish 2.1.1, Ubuntu Linux 9.10

Please provide any additional information below.
I think if you serialize CometSession, it will solve the issue, I will try 
to make the test doing that.

Original issue reported on code.google.com by pablo.mm...@gmail.com on 11 Mar 2010 at 8:45

Attachments:

• glassfishlog.txt

[GoogleCodeExporter]

Unfortunately gwt-comet does not support <distributable/> CometSessions at this
stage. The main problem is the CometSession encapsulates a queue of messages 
which is
continuously changing. I'm not sure how distributing this queue across a cluster
would work.

We would want to ensure current message order guarantees across node migrations.

This is one thing preventing gwt-comet working on Google App Engine.

Something to investigate.

To get around this for now you will have to use the Direct Model
http://code.google.com/p/gwt-comet/wiki/GettingStarted#Direct_Model which does 
not
require sessions. You have to manage your own message distribution and queuing.

Original comment by rich...@zschech.net on 11 Mar 2010 at 10:46

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Ok, I will try that, is there any example on the source of doing that 
implementing a 
queue of messages like you did with CometSessionImpl?

Original comment by pablo.mm...@gmail.com on 12 Mar 2010 at 11:01

[GoogleCodeExporter]

Got it working, if you want I can modify the Chat example to use the direct 
approach, 
so you can provide the two types...

Original comment by pablo.mm...@gmail.com on 12 Mar 2010 at 8:55