+1 on moving in separate assemblies. And may be it will serve as first step to deprecate Remoting facility. I haven't seen in a while discussions/mentions of this facility. Also, Event Wiring is not too much talked around...
On Wed, Sep 22, 2010 at 10:41 AM, xtoff <[email protected]> wrote: > regardless of the discussion in the other thread, I'm still interested > in your feedback here, so do speak up. > > On Sep 22, 2:48 pm, Krzysztof Koźmic <[email protected]> > wrote: > > Hey, > > > > I want to do some rework for Windsor 3, and slim it down a little, and > > as part of it, I'm considering moving the following facilities out of > > Windsor.dll to their own assemblies (similar to Synchronize Facility) > > > > * Event Wiring facility (because it's not that useful/used) > > * Remoting Facility (because remoting is de-facto obsolete) > > * Factory Support (because with UsingFactoryMethod in the fluent API > > not depending on it, there's no really good reason to use it > > unless you register stuff via XML) > > > > That would mean that only Startable and TypedFactory facilities would > > still live in Windsor.dll > > > > Objections? Thoughts? > > > > Krzysztof > > -- > You received this message because you are subscribed to the Google Groups > "Castle Project Users" group. > To post to this group, send email to [email protected] > . > To unsubscribe from this group, send email to > [email protected]<castle-project-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/castle-project-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
