Ralph Goers wrote: > >>> I believe that the excalibur event package lives on at > d-haven [1]. > >>> Why not use that? > > > > Or we could stick with excalibur-event, if there is nothing > wrong with it. > > > > I believe the major concern is making sure that the Cocoon > core only relies on solid, well-supported components backed > by strong communities. > My understanding, and I could be wrong, is that excalibur no > longer fits that description. > Don't know the answer to that, but: excalibur event is deprecated and no longer used. Fortress that was using excalibur event has moved to d-haven event. We have a possible bug that was reported recently on this list.
> I don't know if that is true of D-Haven Event. The site only > lists 4 members on the project team, however I'm pretty sure > at least two of them are quite active in other open source > projects. Out of curiosity, does anyone know what else might > be using this? Apart from Fortress? Don't know. Ok, let's see what we have: Cocoon is not using the Event package at all, apart from the continuations checker which can be implemented in just a few lines - I did this for 2.2 - apart from that Cocoon does not need it. There are people out there who might be using this package for their own projects - so we can: a) keep it to support possible users although we don't need it. Keeping it might be a little bit difficult as it's already deprecated and the future is unknown. b) replace it with something else, users have to migrate and we then support the users although we don't need it. c) remove it and if a user needs it she can add it as her own component and use it. <HINT>this is not a vote</HINT> Don't know which is best, but I tend to option c) in this case. Carsten
