> HttpSessionListener
> implementation which clears the directory when it receives
> a
> sessiondestroy callback. This will do your cleanup
> automatically and
> does not rely on client-side scripting which sometimes
> doesn't work:
> (Examples: computer shuts off/unplugged,
If it's actually shut off (as oposed to being unplugged) I believe the
OS typically closes the browser window as part of the shut-down
process... at least that's true of Windows -- I can't say for certain
about Unix operating systems, although I can say that if I used them I
think I'd want them to. For much the same reason I like encapsulating
"events" in my code -- there's always that "what if" involved in
terminating it without launching any events associated with it's
termination -- plugins that need to do something when the browser
closes, etc...
> User kills the app,
JS handles this.
> non standard browsers
JS can do a pretty good job of mitigating this.
Although you'r right, an HttpSessionListener event is liable to be
more bulletproof. It's also liable to make anyone who's not well
versed in Java lose their lunch, their hair and their marriage all at
once. :)
s. isaac dealey 954.927.5117
new epoch : isn't it time for a change?
add features without fixtures with
the onTap open source framework
http://www.sys-con.com/story/?storyid=44477&DE=1
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]
