<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Snell, James</title>	<link>http://tc.eserver.org/authors/Snell,_James</link>
	<description>A bibliography of works by Snell, James in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Snell, James</title>
		<link>http://tc.eserver.org/dir/Snell,_James</link>
	</image>
	<item>
		<title>Convert Atom Documents to JSON</title>
		<link>http://tc.eserver.org/30806.html</link>
		<guid>http://tc.eserver.org/30806.html</guid>
		<description>Converting an Atom document to JSON might, at first, appear to be a fairly straightforward task. Atom is, after all, just a bit of XML and XML-to-JSON conversion tools are widely available. However, the Atom format is more than just a set of XML elements and attributes. A number of subtle details can make proper handling of Atom difficult. This article describes those issues and demonstrates a mechanism implemented by the Apache Abdera project to convert Atom documents into JSON and produces a result that is readable, usable, and complete.</description>
	</item>
	<item>
		<title>Call SOAP Web Services with Ajax, Part 1: Build the Web Services Client</title>
		<link>http://tc.eserver.org/27054.html</link>
		<guid>http://tc.eserver.org/27054.html</guid>
		<description>Implement a Web browser-based SOAP Web services client using the Asynchronous JavaScript and XML (Ajax) design pattern.</description>
	</item>
	<item>
		<title>Programming Web Services with SOAP</title>
		<link>http://tc.eserver.org/21655.html</link>
		<guid>http://tc.eserver.org/21655.html</guid>
		<description>The task of creating and deploying web services is really not all that difficult, nor is it all that different than what developers currently do in more traditional web applications. The tendency on all platforms is to automate more and more of the gory details and tedious work in creating web services. Most programmers don&apos;t need to know the exact details of encodings and envelopes; instead, they&apos;ll simply use a SOAP toolkit such as those described here.</description>
	</item>
	<atom:link href="http://tc.eserver.org/authors/Snell,_James.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>