Brett McLaughlin wrote:
>
>
> Service service =
> TurbineServiceManager.getInstance().getService("scheduler");
> // Set up a new event and start the process of execution (timer)
> service.init(myNewEvent);
> service.execute();
>
> No big deal, you still don't see, right? But what if the scheduler is
> distributed, and on another machine? Uh.. oh... but no big deal,
> because the client doesn't request an implementation of a _sepcific_
> service, they request an implementation that conforms to the generic
> _service_contract_!!
I just want to be clear. Are you saying then that *all* calls to a
Service
will be through:
service.init(myNewEvent);
service.execute();
So for example, updating, adding, and removing JobEntries should be
completely hidden
to the client (i.e. all they see/care about is init and execute)? If
this is so, then
shouldn't the objects you pass in init() need to be a type of Command
(then a Service is really a
kind of Command Manager).
I also find - service.init(Object) - a little confusing. To me
init(Object), "sounds" like ( I know it's not your intention) you're
initiating the service with some possible parameters. To me it seems the
execute() should actually be passed the "thing" to operate on.
That's just my .02. Otherwise this is great stuff. As soon as we've
all decided on it, I'll jump in and
switch the scheduler over.
dave
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
