Advertisement
My understanding of phenotropic programming is something like loose coupling between services.
eg. rather than have a client send fixed protocol messages to a server and have it part break if the server doesn't respond properly, send messages that have to be pattern matched and interpretted by the receiver, and have caller pattern match and interpret the results and make the best sense of them it can.
A good example of this is the browser which copes and does something sensible if the HTML it receives from the server isn't perfect.
Is this right? Anyone want to add more details?
eg. rather than have a client send fixed protocol messages to a server and have it part break if the server doesn't respond properly, send messages that have to be pattern matched and interpretted by the receiver, and have caller pattern match and interpret the results and make the best sense of them it can.
A good example of this is the browser which copes and does something sensible if the HTML it receives from the server isn't perfect.
Is this right? Anyone want to add more details?
posted by:
|
Brazil
|
Advertisement
Advertisement
-
Re: what is it?
Mon, February 14, 2005 - 2:57 PMThe current concept of software is brittle, especially at the interface between two routines/programs/systems. We use APIs, protocols, etc., to define the place where software meets software. This highly structured, formalized approach requires more & more support surrounding the moving of the actual data from one place to another.
What's needed is a more organic approach, where each side of the conversation negotiates with the other to find a suitable connection that meets the needs of both. Think of it like two pairs of neural nets (one incoming & one outgoing for each side) that train themselves on each other's datastreams to figure out how to process what they're giving to & getting from each other.
Tim
