> From: "Mladen Turk" <[EMAIL PROTECTED]>
> Sent: Wednesday, May 25, 2005 10:08 AM
> Sure all that is in place, but OTOH the http keep-alive connection *can*
> be opened for several hours or days.
> HTTP/1.1 uses persistent connections by default and you must explicitly
> add the 'Connection: clos
On 5/25/05, Mladen Turk <[EMAIL PROTECTED]> wrote:
> Nikola Milutinovic wrote:
> > [EMAIL PROTECTED] wrote:
> >>
> >
> > Then you're messing it up. HTTP has no paradigm of a session, which is
> > what you need here. HTTP has a very clear request/response model. It is
> > not designed to hold the HT
Nikola Milutinovic wrote:
[EMAIL PROTECTED] wrote:
Then you're messing it up. HTTP has no paradigm of a session, which is
what you need here. HTTP has a very clear request/response model. It is
not designed to hold the HTTP channel open indefinitely and will break
off after a timeout. Time
[EMAIL PROTECTED] wrote:
Please, I need Advice for connections
Hi guys.
I need a technical advice using tomcat 5.0
Presently, tomcat server is used with JBOSS in a solution that
I am developping for my clients.
Users are connecting to the solution by invoking a servlet (runned by tomcat).
Please, I need Advice for connections
Hi guys.
I need a technical advice using tomcat 5.0
Presently, tomcat server is used with JBOSS in a solution that
I am developping for my clients.
Users are connecting to the solution by invoking a servlet (runned by tomcat).
If a user is auhentified, th
