On Thu, Jan 09, 2003 at 01:09:57PM -0800, Daniel Rall wrote: > I will be moving SourceCast to the new Avalonized Fulcrum code at the end of > February. Any service implementations which haven't yet been ported which > are used by SourceCast (e.g. XML-RPC) I will port at that time.
Cool. > I'd also be a fan of seeing the TurbineXxx classes go. I'm +1 on > deprecating them today and removing them in a while. I'm unsure about the > interface classes -- I suppose that those should probably stay. Sounds like a good idea. > The non-Avalon interface to the old-style Fulcrum core which John McNally > was able to preserve should also stay in the mainline for some time to come. Okay, so like along with the XML-RPC component, Intake component, etc., we'll have a LegacyFulcrum component that loads old school Fulcrum services? I think moving the logic out to its own component instead of being in the core makes sense...initially, I haven't thought it all the way through it. Which brings up the point of the core/container. Fulcrum currently has the BaseServiceBroker/FulcrumContainer/etc., but I take it we don't really want for Fulcrum to have it's own container. Perhaps getting rid of BaseServiceBroker and relying totally on a wrapped Avalon container (e.g. how FulcrumContainer uses ECM...though I'd really like to rename FulcrumContainer, as it insinuates we have our own container. Something more like ContainerBootstrap or what not) is what I'm thinking and from what I can tell, is what is done so far, just a little crufty what with the old BaseServiceBroker and singleton patterns still there. > I wouldn't be adverse to seeing a branch which dumps that stuff entirely (as > per Duncan's "Rules for Revolutionaries"), but I think that Jason van Zyl > has already done a good deal of that work with his own Avalon container > (Plexus?). I haven't looked in on Plexus lately...at one point I get the impression that Jason was using it to play with Avalon stuff until something better came out of Avalon (e.g. Fortress/Merlin). Is this still the idea? Or is Turbine/Fulcrum/Torque looking at using Plexus as it's primary container? > Woo hoo!! Go Stephen! Hehe, sounds good. We'll see what I can get around to doing. Thanks, Stephen -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
