After some digging I found why this is happening: Atmosphere is
asynchronous, and perthreadManager.cleanup() call happens before Atmosphere
handler invocation.
I'm sort of confused - is there any way around this? Any suggestions?
On Mon, Sep 14, 2020 at 7:43 PM Ilya Obshadko wrote:
> Hi!
>
> I'
Hi!
I'm integrating Atmosphere in my project, but without using
tapestry-atmosphere (I intend to keep Atmosphere separate from Tapestry
itself, much similar to RestEasy integration).
I have managed to get it working, however I have issues propagating
@PerThread services (like RequestGlobals) to A
