Use of HttpSession in atmosphere

[vamsikkancharla]

Dear Team,
We are using Atmospehere framework in our product for Async Push Notifications using Websockets/Long-polling.
In our Product, we support multiple application sessions in a single browser session using the concept of path based cookies.
i.e if we hit (From same browser different tabs) http://host:port/app/abc , http://host:port/abc/xyz we will have separate application sessions but single JSESSIONID as the JSESSIONID is container managed.
In this case both the sessions uses different Websockets and same Jsession ID. And our notifications/atmospehere broadcasters are tied with application session cookie.

We noticed that Atmosphere internals uses HttpSession, which is tied with JSESSIONID.
Could you please let us know what do we store in HttpSession and what scenarios will fail if we use shared JSESSION accross multiple application sessions?