Jan,

http://stw.castleproject.org/Windsor.Extension-Points.ashx

Anything missing from the list?

On 3/09/2010 11:50 PM, Jan Limpens wrote:
handler selector? huh?

problem with windsor is, that it is so huge that I always remember the story of the three blind men and the elefant.

I have a look at this, now that I finally learned about IInterceptors :)

2010/8/30 Krzysztof Koźmic <[email protected] <mailto:[email protected]>>

     re: replace behind the scenes.

    why not use a handler selector then?

    Problem with removing a component is that it has far reaching
    consequences.


    On 31/08/2010 12:32 AM, Jan Limpens wrote:

        We are using it in a context, where child containers would be the
        better approach any way. So, if a customer needs a
        customization of a
        service, during bootstrapping, we first remove the default
        service and
        then add the customized version. Still, I think it would be a good
        feature to be able to replace the implementation of a registered
        service behind the scenes.

        2010/8/30 Mauricio Scheffer<[email protected]
        <mailto:[email protected]>>:

            I'm not using it either.
            --
            Mauricio
            2010/8/30 Jonathon Rossi<[email protected]
            <mailto:[email protected]>>

                Just checked, we aren't using it either.

                2010/8/29 Krzysztof Koźmic<[email protected]
                <mailto:[email protected]>>

                     Hey guys.

                    I'm looking at some more serious modifications
                    that we could do for
                    Windsor 3.0 and one thing that I'd really like to
                    get rid of is
                    IKernel.RemoveComponent (not to be confused with
                    IKernel.ReleaseComponent or
                    IWindsorContainer.Release). I'm talking about
                    method that is the opposite of
                    Register, not Resolve.

                    The method is very flawed, not thread safe, has
                    bugs, its usability is at
                    best questionable and getting rid of it (so that I
                    can make an assumption
                    that once a component is in the container it can
                    not dissappear) would
                    enable me to get rid of lots of code and make some
                    performance
                    optimizations.

                    So my question is - what do you think about this
                    idea - did anyone of you
                    ever really used this? If so - why and for what?

                    feedback greatly appreciated, thanks

                    --
                    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]
                    <mailto:[email protected]>.
                    To unsubscribe from this group, send email to
                    [email protected]
                    
<mailto:castle-project-users%[email protected]>.
                    For more options, visit this group at
                    http://groups.google.com/group/castle-project-users?hl=en.



                --
                Jono

                --
                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]
                <mailto:[email protected]>.
                To unsubscribe from this group, send email to
                [email protected]
                <mailto: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]
            <mailto:[email protected]>.
            To unsubscribe from this group, send email to
            [email protected]
            <mailto: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]
    <mailto:[email protected]>.
    To unsubscribe from this group, send email to
    [email protected]
    <mailto:castle-project-users%[email protected]>.
    For more options, visit this group at
    http://groups.google.com/group/castle-project-users?hl=en.




--
Jan
--
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.

--
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.

Reply via email to