[Seaside-dev] [Dolphin] Use of Delay on CTPusher class>>startUp and pingProcess

Julian Fitzell jfitzell at gmail.com
Mon Sep 21 12:40:35 UTC 2009


Ah, ok. Fair enough.

On Mon, Sep 21, 2009 at 11:35 AM, Lukas Renggli <renggli at gmail.com> wrote:
>> Hmm... but you understand why there *should* be a problem, right?
>
> No.
>
>> I mean I haven't tested this very thoroughly or even looked at the
>> code. I just got subclass should implement error when I updated Comet
>> before Pharo-Comet (which is the order we use everywhere else). I
>> don't know why it would have been working before and not now.
>
> Aha, now I understand. In your image the ping process was already
> running when you updated the code. Then you got a mismatch between
> Comet-Core and Comet-Pharo-Core. Since normally when loading the
> packages the Comet ping process is not running, there should be no
> problem loading the code.
>
>> Is there something wrong with doing it when the server adaptor starts,
>> though? I think we should be avoiding class-side initialize methods
>> whenever possible anyway...
>
> There is no class-side initialize method involved into this. Comet
> only registers for image startUp/shutDown, but it does not do anything
> else.
>
> Lukas
>
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>


More information about the seaside-dev mailing list