I'm not sure exactly how DWR is implementing its reverse Ajax, but are you sure about the following?
Originally posted by Jim Bassy:
It was my impression that reverse ajax opens another session and keeps it open.
Why would it create a new session? And the phrase "open a session" doesn't really mean much. Are you confusing requests and sessions?
Without knowing any details of the implementation, I might guess that the long-standing connection mechanism used by DWR is keeping the session alive because the session will only start its timeout counter when there is no activity. Any open request(s) will likey count as activity.
[ June 23, 2008: Message edited by: Bear Bibeault ]