I consider a self-described / auto-descriptive service as a good thing in a SOA architecture, since (almost) everything you know to call the service is present in the service contract (such a WSDL). Sample of a non self-described service for me is Facebook Query Language (FQL http://wiki.developers.facebook.com/index.php/FQL), or any we...
What feature(s) of ASP.Net MVC can replace the way events can be used in Webforms to support loosely coupled components? For example, take a simple pager control in Webforms: A page number is clicked Pager fires off a "PageChange" event with the new page number This subscribing page/control received the event and handles initiating a ...
Hi, We're developing a layered web application. The specs: 3 layers, data layer, business layer, ui layer. Programmed in C# Data Layer uses the entity framework Currently we plan on having the data layer return IEnumerable<T> to the business layer via linq 2 entities, and the business layer will return data to the ui layer. Sinc...
When I look at ASP.NET MVC projects I everytime see loose coupled architecture. For what do I need a loose coupling in a web architecture (if I do not make unit tests)? What are advantages and disadvantages of this? ...
Currently my layered ASP.Net application is structured like this: Entity Layer (data model classes auto-created using T4 against my Entity Data Model (edmx) in the data layer) Data Layer (Containing the edmx) Business Layer UI Layer The entity layer is referenced in all layers. My UI layer uses MVC 2. I'd like to implement the uni...
Let's say I have three object A, B, C. B is the implementation of following interface: interface D { event EventHandler<OrderEventArgs> OrderCreated; event EventHandler<OrderEventArgs> OrderShipped; } I would add two functions in B which will raise the events in the interface. class B { RaiseOrderCreated(); RaiseOrderSh...
I'm trying to code an application that can work for several projects. I'm facing a problem that I have always to specify the name of the project when I do the imports like doing import some_project_name.models inside my app, how can I overcome this coupling so that I can use the app in several projects? ...
I am struggling to see the real-world benefits of loosely coupled code. Why spend so much effort making something flexible to work with a variety of other objects? If you know what you need to achieve, why not code specifically for that purpose? To me, this is similar to creating untyped variables: it makes it very flexible, but opens ...