<?xml version="1.0" ?>
<rss version="2.0">
<channel>
	<title>Phil Dawes Stuff: REST</title>
	<link>http://phildawes.net/blog//tag/REST/</link>
	<description>Entries of Phil Dawes Stuff tagged with 'REST'</description>


	<item>
		<title>10 things to change in your thinking about XML protocols</title>
		<description><![CDATA[
<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>
]]></description>
		<link>http://phildawes.net/blog/2006/06/21/10-things-to-change-in-your-thinking-about-xml-protocols/</link>
		<guid>http://phildawes.net/blog/2006/06/21/10-things-to-change-in-your-thinking-about-xml-protocols/</guid>
	</item>

	<item>
		<title>Server length limitations on HTTP GET URLs</title>
		<description><![CDATA[
<p>I just did a little bit of testing at <a href="http://www.drkw.com/">work</a> and thought I'd dump it here for future googlers:</p>

<p>We've got an internal app team building some REST webservices and they wanted to know the practical limits of GET URL length. Now browser limits are <a href="http://support.microsoft.com/default.aspx?scid=KB;en-us;q208427">well known</a>, but since the clients will be programatic they wanted to know what the server limits were.</p>

<p>They're using java and so I tested apache+ajp+tomcat and apache+ajp+jboss, followed by tomcat and jboss standalone. (apache 2.0.49, jboss 4.0.0, tomcat 5.5.9)</p>

<p>In all cases url lengths of 8000 characters were processed correctly, but 8100 characters consistently caused failures in the webservers generating either a 500 error or just closing the socket.</p>

<p>Having thought about it, this could be a tomcat thing since jboss 4.0.0. embeds tomcat as the internal container. If I get the chance I might get round to trying a standalone apache (e.g. using CGI or something). (The http spec <a href="http://www.boutell.com/newfaq/misc/urllength.html">puts no limits on URLs</a> btw)</p>
]]></description>
		<link>http://phildawes.net/blog/2006/05/09/server-length-limitations-on-http-get-urls/</link>
		<guid>http://phildawes.net/blog/2006/05/09/server-length-limitations-on-http-get-urls/</guid>
	</item>


</channel></rss>
