ScheduledExecutorService, no question ... If you don't, I would write it with an someObject.wait(sessionTimeout) and someObject.notifyAll when you ping the session to keep it alive, at which point your code can decide if it needs to perform its action or resleep. Definitely don't poll, but regardless, I wouldn't write this yourself. java.util.concurrent will do something better than either of us can come up with. The guys who wrote that stuff are pretty damn smart.
I see what you're saying about java.util.concurrent, the more I learn about it, the more I like it and feel comfortable relying on it. Will go with that option...
Thx, F _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
