Sorry may be I did not explain it clearly. I am not try to do SOA, but more as an enhancement to MVC. What I want to build is a normal application, like suppos

Sorry may be I did not explain it clearly. I am not try to do SOA, but more as an enhancement to MVC. What I want to build is a normal application, like suppose I want to build a authentication system, I will have a display component, validation component and a securit provider component, data store component. Each of these components will be independent but the framework will load these components and will connect them together to implement final functionality. What will be the benefit for developing using this component approach will be reusability and changeability. Another advantage will be that I can change the Metadata and rewire the components to implement different functionality for certain user groups. Since the framework language of assembly is very simple, namely, Define a Context, Add Components into that Context Configure Components in that Context Link Components in that Context I believe this will cleanly separate assembly from coding of the component but increase the productivity and relibility of the final application feature. What you have suggested is the components are distributed, which creats a reliability and connectivity problem. What I am trying to do is developing instead of a single monolithic application, why we cannot split the application into individual components and only the framework will stitch this together to give the final functionality. Do you think such a framework will be useful?