Does comet_request keep a LiftSession alive? (I think no)

[Christopher Oman]

We are using 3.0-M1 currently. I am seeing some behavior which seems to be related to the default idle session of 30 mins. I have a comet actor that is pushing updates to the page about once per second. After 30 mins, I see in the network tab that the comet_request requests start getting 404 backs. Eventually, the page refreshes and everything is back to normal.

However, before the refresh, the UI is in a state that we currently get back to (I know, bad UI design). What do I need to do to keep the session from being idle in this case? I do see the periodic messages from lift for the GC.

Is this something that is perhaps fixed in a later 3.0 milestone?

Thanks,

Chris

[Antonio Salazar Cardozo]

This sounds altogether wrong. The presence of a comet connection should be enough

for the session to be alive. Try turning the session timeout down to something much

shorter (say, 2 minutes, or even 30s) and see if the 404s start happening immediately.

If so, it would be super-handy if you could post an example project for us so we can

do some debugging.

Thanks,

Antonio

[Christopher Oman]

Thanks for getting back with me. I will attempt to put together an example project soon.