was concerned about performance and complexity of my alternative
solution (separate executable + tcp socket + custom protocol or at least
some rpc which would use a lot of xml).
> Kamil Burzynski a écrit :
>> Hello,
>>
>>
>>> Please read the other responses to this t
de against current version of Tomcat, though I
would like a clean solution. So, it seems, that I'll do standalone
server and then webapp will connect to it via some protocol (I am not
familiar with java world enough to know if any good rpc is there - most
probably it is).
Thanks for all answer
Thanks for quick reply. So, it seems, that I have guarantee, that my
servlet once started, will live as long as my webapp/tomcat will live..
this is exactly what I was looking for.
--
Best regards from
Kamil Burzynski
-
To start
1 month of inactivity, or so much requests arrive
that out-of-memory will happen?
Maybe I should create some background thread or socket or whatever?
Any solutions appreciated, thanks in advance.
--
Best regards from
Kamil Burzynski
--
