2) Be the Container in chapter 8, the third example will not work for the same reason that the first example doesn't work--because the attribute is at Request Scope, and the default scope is Page scope.
OK - Let me put it more clearly; In the test - if I see the phrase "init-parameters" - should I ALWAYS think of this a servlet-init-parameters - unless - of course - otherwise stated?
Is that totally op to the container to decide ? - or is the servlet destroyed when the final thead is dead?
My current project is with servlets/jsp...
Kathy & Bert have an effective writing style .. lot of credit should go to Kathy Sierra & Bert Bates for my scjp..It is especially helpful for people who are working..
I hope I feel the same for HFS.
And if you do implement a timeout, you will have to change the comments above the lock method to indicate that it will timeout - which to me seems to indicate that you will not be implementing the method the way that Sun envisaged it.
, some locking-specific additional timeout mechanism seems at least to be defendable.
The client will renew each lease when it is halfway expired. If the lease interval is too short, the client will waste a lot of network bandwidth needlessly renewing its lease. If the lease interval is much too short, the client will be unable to renew the lease in time, and the exported object may be deleted as a result.