> From: Berin Loritsch [mailto:[EMAIL PROTECTED]] > > 1) Identify the absolute minimum requirement for Avalon > compliance. Currently this is be the ability to > handle Thread Safe components (aka singleton), and > full support for the established Avalon lifecycle. > Beyond that, we need to come to consensus.
Even the lifecycle isn't 100% solid. Lately we've had some discussions regarding the Context interface. It needs a better definition, and we need a better interpretation of it and understanding of just what it is. I suppose this is something that will be done throughout, though, but I'd like to get it going by step 1. /LS -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
