Hi, At the moment in an app of mine I'm using a container mechanism basing on Castle.Core. The main idea was, as far as I understood it, similar as the idea behind windsor. The management mechanisms are not as mature and there were no lifestyles planned. Since this is much beautifuller in windsor, I thought about exchanging my own mechanism by windsor. The problem I faced, windsor seems not to share my main focus by designing my mechanism.
I wanted to increase stability by separating the, as I call them, services by running them in separate threads and completly control/proxy the communication between the containers. Later even separate them by different appdomains, so they get hotswap- and runtimescleable even over machineborders for beeing able to do loadbalancing and to not shutdown daemons for updating. My question is now, how feasible is it to switch to windsor and invest developmenttime to create new lifestyles for it implementing such possibilities? https://github.com/RalphBariz/RalphsDotNet/tree/master/Service.Base/RalphsDotNet.Service for a peek at my servicing mechanism(excuse me for my lazyness concerning documentation, happily it's not that big and I had to rush a bit). BR Ralph -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/castle-project-users. For more options, visit https://groups.google.com/d/optout.
