&
On the concept of contracts and contracts, I think we need "interface phasing". Having a phased relationship between two parties.
It is imperative that objects and at a higher level, an Application, can change the way they interact by who or what is accessing them.
An object should present itself differently to different audiences. Imagine a developer seeing a specific interface, but not a user, or IDE vs developer. Its not role based, because it could be different per application to application communication, although a similar effect can be achieved.
The concept is simple.
I think that coding today suffers from
-
Repetitive nature of structural elements: for example: creation of large Object Models, classes, properties, collections and so on.
-
Creating Object models with no separation of Context or concerns. I want an object to 'share' code, but for different reasons. Cross-Cutting. Yes, I can create a new object and share code, but that's not always the answer. Imagine two object models, where one is a Facade of the first. I want to simply map the one to the other, not create the entire structure for it again.
-
Different ways of extending components. Different ways of creating add-ins, Custom B2B, Adaptors, Bridge patterns etc. It can all be made easier, if we used a "Global extension object system"
-
The 'under the hood' 'abstractions, keep changing - not for the better or necessarily for the worse, but for no distinct benefit.
-
Contractinitis - Nothing works unless its all explicit. In .NET, can't call the web service with your Person Object, cause its not the same namespace etc.
Create automatic and dynamic proxy layers based on metadata and intention of communication. The code is then 'assembled' and made ready for the communication. The code is assembled from existing non contextual code that can fit into a common proxy container and interact.
On a simple level, imagine, you create SOA like methods, stateless and they are formulated by the runtime into a new object that looks like the one required.
This is not the complete answer, but we really need to get to 'smarter relationships' rather than contracts.
See
Lack of MetaData on code and .NET Framework libraries Read
Evolution, Architecture, and Metamorphosis - A great piece of work.
Tags: