-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob,
On 1/21/2010 8:36 PM, Bob Hall wrote:
> --- On Thu, 1/21/10 at 7:26 AM, Christopher Schultz
> wrote:
>
>>
>> If you access the session at all, it counts as a "touch",
>> thereby
>> extending the life of the session. It's not possible to
>> "pe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 1/21/2010 5:07 PM, Pid wrote:
> On 21/01/2010 15:26, Christopher Schultz wrote:
> Pid,
>
> On 1/21/2010 3:32 AM, Pid wrote:
On 21/01/2010 04:45, grailcattt wrote:
>
> That is exactly what I ended up doing and it is working well.
--- On Thu, 1/21/10 at 7:26 AM, Christopher Schultz
wrote:
>
> If you access the session at all, it counts as a "touch",
> thereby
> extending the life of the session. It's not possible to
> "peek" at the
> session without "touching" it AFAICT.
The Session timeout can be set when the response
On 21/01/2010 15:26, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 1/21/2010 3:32 AM, Pid wrote:
On 21/01/2010 04:45, grailcattt wrote:
That is exactly what I ended up doing and it is working well. I was
hoping
for a solution that used tomcat session manage
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 1/21/2010 3:32 AM, Pid wrote:
> On 21/01/2010 04:45, grailcattt wrote:
>>
>> That is exactly what I ended up doing and it is working well. I was
>> hoping
>> for a solution that used tomcat session management rather than
>> managing my
>> own
On 21/01/2010 04:45, grailcattt wrote:
That is exactly what I ended up doing and it is working well. I was hoping
for a solution that used tomcat session management rather than managing my
own session timeouts, but it works well.
If you put the poll servlet in a separate app and are NOT using
That is exactly what I ended up doing and it is working well. I was hoping
for a solution that used tomcat session management rather than managing my
own session timeouts, but it works well.
--
View this message in context:
http://old.nabble.com/Polling-and-session-timeout-tp27129549p27252791.ht
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael,
I've been seeing this message on the list for a few days, and haven't
responded because I didn't have any suggestions for you. Since nobody
has answered, I'll go ahead and give you my thoughts.
On 1/12/2010 10:42 AM, grailcattt wrote:
> I ha
