on 2/11/00 10:50 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> A Client should always call init() - execute(). However
> the service developer could have a service the does some one
> time initialization on the first call but should always at a minimum, check
> the isReady flag. Let's say I create an Object pool. In the init the client
> passes the object to pool. My init would first check to see if the pool is
> started (isReady) then maybe check to see if
> this is the proper type of object for the pool (instanceof) and then
> forward the object to the actual execute.
I think that John and agree that calling init()/execute() is a bad idea. To
many places for a developer to make mistakes as well as to much code to
write as well as potential issues with synchronization.
I also have talked to John a bit more about what Brett is proposing and I
think that I'm going to now totally -1 one it after further consideration.
So, consider the current stuff on -1 for now until I am able to propose
another solution (it will be soon, I promise). In the mean time, I suggest
that you continue to implement your services exactly the same way that we
have been doing so so far.
-jon
--
Come to the first official Apache Software Foundation
Conference! <http://ApacheCon.Com/>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
