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 all, just a quick question...
Once a Tapestry service implementation gets instantiated, and that
service's status moves to "realised", at what point does that
implementation get destroyed?
Tapestry instantiates a service implementation the first time a service
method gets called, and I'm
