Jon Stevens escribió:
>
> Ok,
>
> Just so you know, I just got through with a few fairly major changes to the
> way that Services works and it is much cleaner now. I also tested a lot of
> the functionality so I know that things are working pretty well.
>
> on 1/28/01 1:13 PM, "Raphaël Luta" <[EMAIL PROTECTED]>
> wrote:
>
> > I agree that Turbine Services should probably make sure the late init is
> > called on an object when early init is complete
>
> If you don't call setInit(true) in early init, then late init() will be
> executed. I just tested this a few minutes ago and it works.
>
> > I still agree with you that TurbineServices should ensure that late init is
> > always
> > called when early init is complete to avoid race conditions and highlight the
> > kind
> > of bugs we have
>
> It is definitely called if getInit() returns false.
>
> In fact, here is the code...
>
> service = getServiceInstance(name);
> if(!service.getInit())
> {
> notice("Initializing service (late): " + name);
> service.init();
> }
>
But what if the service is half way early initialization? That is the
problem we get. I will check your new code, to ensure there are no
problems with this.
Our problem comes from the fact that early initialization of some
services is fairly slow, so race conditions are easy to happen.
> -jon
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/[email protected]/>
> List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
