Open spring-operator opened 18 years ago
Keith Donald commented
Currently conversation expiration occurs when the user session expires. We'll revisit adding our own expiration service in the 1.1 timeframe. In the meantime, relying on container-provided session expiration should be sufficient for most cases.
Jon Osborn commented
It would be interesting to have a shorter expiration for 'old' conversations...particularly because, for some applications, the current conversation may be worked for a long period of time and the 'old' ones are dead and just taking up space. Setting maxConversations =1 doesn't always work either because the transition from old to new may require that the back button work across the transition.
GuoJian Zhang opened SWF-192 and commented
Affects: 1.0.4
2 votes, 3 watchers