[Seaside] Announcements/Seaside continuations collision in newer
sebastian at flowingconcept.com
Fri Sep 9 13:20:01 UTC 2011
Isn't the plain events mechanism forkless and essential to the core of the system already?
if you introduce that fork you break not only seaside but all artifacts of all the people that will rightly assume the current process between event and reaction is the same
On Sep 9, 2011, at 7:13 AM, Tudor Girba wrote:
> Igor and Stef can provide more details.
> The reason for forking is that even if one announcement breaks, the others should still be announced. Announcements are used for the functioning of the core of the system and this means that even if you register new objects, the core mechanisms (such as package management) should continue to work.
> It would be great if Seaside would work with these, and now depend on another framework.
> On 9 Sep 2011, at 06:38, Philippe Marschall wrote:
>> 2011/9/8 Esteban Lorenzano <estebanlm at gmail.com>:
>>> (yep, I'm copying tree lists because I think is a vm problem, but can be a seaside problem, or a pharo problem)
>>> (yes, it can be MY problem too... but I don't think so... ;)
>>> I'm having this really, really strange problem (because it was working before, and I do not change anything... so, maybe a change in latest changes on pharo 1.3, the version I'm using, is the cause)...
>> The announcements in the latest Pharo 1.3 don't work with Seaside
>> anymore. For some reason they fork them instead of running them in an
>> exception handler.
>> seaside mailing list
>> seaside at lists.squeakfoundation.org
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside