Cart
[Home] [By Thread] [By Date] [Recent Entries]
On Mon, 16 Dec 2002 11:52:03 -0800, Paul Prescod <paul@p...> wrote: > Maybe the problem isn't with either the APIs or the protocols/formats. I propose > that one must choose: either the API is primary or the protocol/format is > primary. If you decide the API is primary then the wire format will tend > to be pretty ugly and hard to decipher. It will probably tend to degrade > over time because it "doesn't matter much." Try decoding IIOP ... or, > increasingly, SOAP to see this phenomenon in action. That's an awfully good thought ... I'll have to think about it more ... > I believe that it is impossible to optimize *both* API and data representation/protocol. Reminds me of the "syntax - data model duality" I've proposed ... sortof an uncertainty principle of formats vs APIs. There's something deep here that I don't think software engineering has a good handle on right now. XML practice is OOP-ish in some ways, but antithetical to OOP in others. Paul has a bit about "Resource Oriented Programming" on his website, as I recall, which is useful. Does someone with a better handle on recent developments in computer science or software engineering have a better answer, or compelling refutation to the assertion that we're in somewhat uncharted theoretical territory here?
|
