Great recommendation. I hadn't played with XOM before -- it looks very nice and I will try it out in an upcoming project! I'd still argue that it is good to understand the W3C DOM API, whether or not one actually uses it, because it is ubiquitous and largely similar in many languages and environments.
Empirically, I think the spartan nature of REST designs often encourages adopters to use very simple markup for representations. Simple XML and JSON documents are quite easy to create even with bad or no tools, and the real advantages of more powerful and language-adapted APIs may not show up as critically for users who have never heard of, say, an XML namespace. - Rob On Sat, Mar 15, 2008 at 1:09 PM, Steve Loughran <[EMAIL PROTECTED]> wrote: > - Xom by Elliotte Rusty Harold is very elegant, and fairly extensible, > though ERH does have very strict ideas about what should and should > not be allowed. You have to get along with that. > > I'm mostly a Xom fan myself. Were I to use restlet more, I'd end up > doing a Restlet/Xom binding to alongside my Xom-based SOAP stack. > > -steve >
