<?xml version="1.0" encoding="utf-8"?>

<feed xmlns="http://www.w3.org/2005/Atom">
<title>Phil Dawes Stuff: xml</title>
<id>http://phildawes.net/blog//tag/xml/</id>
<link rel="alternate" type="text/html" href="http://phildawes.net/blog//tag/xml/" />
<link rel="self" type="application/atom+xml" href="http://phildawes.net/blog//tag/xml/atom.xml" />
<author><name>Phil Dawes</name></author>
<updated>2006-06-21T11:28:00Z</updated>


<entry>
  <title type="html">10 things to change in your thinking about XML protocols</title>
  
  <category term="General" /> 
  <category term="REST" /> 
  <category term="programming" /> 
  <category term="workfriendly" /> 
  <category term="xml" />
  <id>http://phildawes.net/blog/2006/06/21/10-things-to-change-in-your-thinking-about-xml-protocols/</id>
  <updated>2006-06-21T11:28:00Z</updated>
  <published>2006-06-21T11:28:00Z</published>
  <link rel="alternate" type="text/html" href="http://phildawes.net/blog/2006/06/21/10-things-to-change-in-your-thinking-about-xml-protocols/" />
  <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
	
<p><a href="http://www.xmldatabases.org/WK/blog/2287_10_things_to_change_in_your_thinking_when_building_REST_XML_Protocols.item">This post</a> hits the nail on the head. I've been blathering on about some of this stuff at work* for a while: Don't tie your protocol to your programming language, protocol is the most important thing in a distributed system, make data as simple/flexible/loosely-coupled as possible, don't constrain yourself with schemas. Now I've got something to <a href="http://www.xmldatabases.org/WK/blog/2287_10_things_to_change_in_your_thinking_when_building_REST_XML_Protocols.item">link to</a>.</p>

<p>N.B. I don't think this is just applicable to protocols - also data storage. Serialized objects and O-R mapping tools can seriously louse up your data if you're not careful.</p>

<ul>
<li>usually to people that aren't interested</li>
</ul>

      </div>
  </content>
</entry>




</feed>
