« Paste XML as Serializable Type | Main | My MIXperience: Don MacAskill »

2007.05.03

TrackBack

TrackBack URL for this entry:
http://www.typepad.com/services/trackback/6a00d83451806669e200d834febf5453ef

Listed below are links to weblogs that reference Some Interesting History:

» Design for the real world from Bill de h├ôra
Jeff Newsom: "I find this interesting. So, basically, at the end of the day, there is a baseline understanding of how the web was designed and currently works that was largely ignored/dismissed in the soap world and specifically in the... [Read More]

Comments

Patrick Logan
"Do we need contracts?" Always. The misunderstanding is in answering "what is a contract?" Design-time checked overspecifications are not the only form of contract. For example, the HTTP spec is a contract. The Atom Protocol spec is a contract that builds on that. If I were to build an order management system on top of the APP, I could give you a specification that builds on APP. As you noted, an "SDK" or even just "a set of tests" is often a sufficient executable format for those contracts. Given my order management spec and a reasonable set of tests that excercise it, developers should not have any trouble using that order management system.

The comments to this entry are closed.

November 2008

Sun Mon Tue Wed Thu Fri Sat
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30            
Blog powered by Typepad

We Like