Cannot access SessionId from BayeuxContext about cometd HOT 10 OPEN

I think it can be restored.

Out of curiosity, what do you use the session id for?

from cometd.

We use sessionId to keep track of connections, so messages can be published to correct users and to be able to do cleanup.

BTW. Do you have a rough idea when 8.0 will be GA? Few weeks? Few months? If it helps, I have not seen any issues with 8.0 that were caused by CometD itself. (Other then missing getSessionId) Jetty 12 caused some issues, mainly because handshaking is now done asynchronously (instead of inside of spring framework's filter chain) so we lost Security context and one of the filters (ShallowEtagHeaderFilter) was causing content-type to not be set correctly but again, those were not caused by CometD itself.

Thanks,

wojtassi

from cometd.

We use sessionId to keep track of connections, so messages can be published to correct users and to be able to do cleanup.

But you cannot keep track of connections using the HTTP session id.
It would be the same for all the connections from the same client, so you could only count different clients, not connections.

CometD 8 final is not far away, we need to decide on few things and restore Spring integration.
Thanks for the feedback on CometD 8 and Jetty 12.
Please report your problems in either project, if any, as it will help to fix them sooner.

from cometd.

But you cannot keep track of connections using the HTTP session id.
It would be the same for all the connections from the same client, so you could only count different clients, not connections.

In our case "connection" is misnomer, our code's connection is basically a multimap of sessionid to Bayeux ServerSession.

Thanks for the answer and sorry for confusion.

from cometd.

In our case "connection" is misnomer, our code's connection is basically a multimap of sessionid to Bayeux ServerSession.

Consider that for the same HTTP session id, you can have multiple ServerSessions (for example, 2 browser tabs).

from cometd.