Page 1 of 1
BypassIdleTimeout:Option
Posted: 10 Jun 2009, 08:54
by orthiac
Currently this is built-in and available only for 'isAdmin' property.
I think it would be nice to allow this as an option for the new types that could be in future release.
Example:
Code: Select all
<BypassIdleTimeout>
<mod>true</mod>
<npc>true</npc>
<guest>false</guest>
</BypassIdleTimeout>
I think this would be helpful to a lot of people based on the number of issues I've seen on the forum here.
Thank you for listening,
- Mike
Posted: 11 Jun 2009, 06:21
by Lapo
Hi,
thanks for your submission.
I agree but I wouldn't do it this way.
Shutting down the system for a whole class of users is dangerous and can lead to problems.
It would be much easier to simply have an option on the client side like:
This would allow for "transparent" keep alive system, yet the server would be able to remove the user if and when the client connection goes down (since the keep alive signal would cease)
Posted: 11 Jun 2009, 08:14
by orthiac
Lapo wrote:
Shutting down the system for a whole class of users is dangerous and can lead to problems.
Isn't that what is done already for the admin type user?
Isn't it better to handle a "No timeout" for a group like NPC, than to have to force generated traffic to prevent a User from falling off when you know, in most cases, it is a user that should be "on" all the time.
Since the original timeouts, you've added "Force Logins" and "Socket Timeouts" to assist with stuck sessions as well.
Am I mistaken in thinking that <MaxSocketIdleTime> could be used to handle a lot of lost connections instead of IdleTime?
- Mike