Not sure why you think it will break the API, as I could not find anywhere
the "idleTimeout" being documented as maximum idle time. Below is the
Javadoc from the ListenerFactory:
* Set the number of seconds during which no network activity
* is allowed before a session is closed due to inactivity.
*
* @param idleTimeout The idle timeout in seconds
So, to keep things simple, we should just mark it as a bug and make it the
default timeout. Also, pre 1.0 releases worked fine with listener timeout
set to a finite value and user timeout left at zero. so, I guess the issue
is with 1.0/1.0.1.
Sai Pullabhotla
www.jMethods.com
On Tue, May 26, 2009 at 1:00 PM, Niklas Gustavsson <[email protected]>wrote:
> On Tue, May 26, 2009 at 7:01 PM, Johannes Katelaan <[email protected]>
> wrote:
> > I absolutely agree with you. The listener timeout should be a default
> > timeout.
>
> Since this would break our API, it's not something we can do for the
> 1.X series. So, if we want to introduce a default idle time, in
> addition to the existing maximum idle time, it needs to be a new
> configuration.
>
> /niklas
>
