<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://philmccarthy.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Phil McCarthy</title>
 <link>http://philmccarthy.sys-con.com/</link>
 <description>Latest News from Phil McCarthy</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Thu, 10 Dec 2009 14:21:37 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Creating a ColdFusion Web Service</title>
 <link>http://philmccarthy.sys-con.com/node/351874</link>
 <description>We&#039;ll duplicate our PHP Web service in ColdFusion now using XMLRPC.CFC to format our XML response and the CFJSON.cfm for our JSON response. This is the ColdFusion equivalent of the PHP Web service we just looked at. It can be accessed in a REST-like manner through the resources URI and expects two variables in the query string: numbers and output. The variable numbers will contain a delimited list of numbers that this Web service will sum and return. To make our return object more complex, we&#039;ll return the original request as well as the sum. You can specify your desired output format by setting output to JSON or XML.&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351874&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 02 Jun 2007 17:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351874</guid>
 <comments>http://philmccarthy.sys-con.com/node/351874#feedback</comments>
</item>
<item>
 <title>AJAX in a SOA</title>
 <link>http://philmccarthy.sys-con.com/node/351904</link>
 <description>A service-oriented architecture isn&#039;t much more than a loosely coupled collection of services - often Web services. Services are defined as a unit of work done by a service provider for a service consumer. One of the ways that SOA achieves that loose coupling is by remaining independent of a given technology (such as PHP or ColdFusion) and hiding the details of the implementation - much like a Web service.&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351904&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 16 May 2007 19:15:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351904</guid>
 <comments>http://philmccarthy.sys-con.com/node/351904#feedback</comments>
</item>
<item>
 <title>Real-World AJAX Book Preview: Advanced Techniques</title>
 <link>http://philmccarthy.sys-con.com/node/351905</link>
 <description>The great advantage of AJAX clients is that they can communicate back to the server without interrupting what the user is doing. This in turn provides the freedom for AJAX clients to talk back to the server far more frequently than in a traditional page-based Web application. This can be exploited to provide a much richer user experience, for example, by providing real-time data updates, &#039;live search&#039; functionality, or validating user input on-the-fly.&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351905&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 28 Apr 2007 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351905</guid>
 <comments>http://philmccarthy.sys-con.com/node/351905#feedback</comments>
</item>
<item>
 <title>Real-World AJAX Book Preview: Using TinyAjax to Create Live Search</title>
 <link>http://philmccarthy.sys-con.com/node/351877</link>
 <description>Using a server-side framework will let you shift some of the processing from the client back to the server. In our example we&#039;ll consume our Web service using PHP and print out formatted HTML. AJAX will be used to handle the request and the response, but the Web service will be processed on the server. One benefit to this approach is that you can avoid the issues involved with an AJAX cross-domain request.&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351877&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 26 Apr 2007 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351877</guid>
 <comments>http://philmccarthy.sys-con.com/node/351877#feedback</comments>
</item>
<item>
 <title>Real-World AJAX Book Preview: Creating a Live Search Web Service with PHP</title>
 <link>http://philmccarthy.sys-con.com/node/351876</link>
 <description>To keep this simple we won&#039;t use a database. Instead we&#039;ll use an array of values. Create a new file, StateList.php, with the following in it:&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351876&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Wed, 25 Apr 2007 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351876</guid>
 <comments>http://philmccarthy.sys-con.com/node/351876#feedback</comments>
</item>
<item>
 <title>Real-World AJAX Book Preview: AJAX Without a Server-side Framework</title>
 <link>http://philmccarthy.sys-con.com/node/351875</link>
 <description>If you already have AJAX-friendly web services in place, or have a complex site with a framework that&#039;s not readily modified, you may find it easier to use a client-side framework like Prototype.js or jQuery. We&#039;ll assume that you have AJAX-friendly web services. Let&#039;s try an example using our PHP web service to add two numbers.&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351875&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 24 Apr 2007 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351875</guid>
 <comments>http://philmccarthy.sys-con.com/node/351875#feedback</comments>
</item>
<item>
 <title>Real-World AJAX Book Preview: Creating an AJAX-Friendly Web Service</title>
 <link>http://philmccarthy.sys-con.com/node/351873</link>
 <description>For our example Web services, we&#039;ll be loosely adhering to the REST principle and creating Web services that are addressable through the service&#039;s Uniform Resource Identifier (URI).&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351873&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sun, 22 Apr 2007 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351873</guid>
 <comments>http://philmccarthy.sys-con.com/node/351873#feedback</comments>
</item>
<item>
 <title>Real-World AJAX Book Preview: Common Server-Side Languages</title>
 <link>http://philmccarthy.sys-con.com/node/351864</link>
 <description>The beauty of Web services being platform-agnostic is that we can use any language to develop them - although there are features to watch for when choosing a language. While a Web service can return data in any format, the title of this chapter is &#039;Building AJAX-Friendly Web Services&#039; and our examples will be returning XML or JSON. In keeping with that philosophy we&#039;ll look at languages with inherent XML support or a JSON library.&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351864&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Sat, 21 Apr 2007 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351864</guid>
 <comments>http://philmccarthy.sys-con.com/node/351864#feedback</comments>
</item>
<item>
 <title>Real-World AJAX Book Preview: Flavors of XML</title>
 <link>http://philmccarthy.sys-con.com/node/351863</link>
 <description>Earlier we compared formatting payloads in JSON versus XML. One of the chief advantages of sticking with XML is that it can be validated, that is, that disparate systems can independently confirm that a given XML document is well-formed and complies with a particular schema. Schemas can be thought of as contracts that define the elements an XML document should contain and what constraints the elements and their values should be held to. Document Type Definitions (DTDs) are an older schema format that&#039;s losing favor among developers because of its lack of support of namespaces. Additionally, its successor, the XML Schema Definition (XSD), is well-formed XML and uses a far richer datatyping system.&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351863&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 20 Apr 2007 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351863</guid>
 <comments>http://philmccarthy.sys-con.com/node/351863#feedback</comments>
</item>
<item>
 <title>Real-World AJAX Book Preview: Building AJAX-Friendly Web Services</title>
 <link>http://philmccarthy.sys-con.com/node/351862</link>
 <description>When developers first realize what an AJAX client can do, they are often especially excited about its potential in playing the role of the View or even the Controller in the Model-View-Controller (MVC) patterns of application development, with Web services providing the Model layer. If you&#039;re unfamiliar with the term, MVC is a paradigm used by software developers to design user interface code (the View) that is decoupled from the data objects it displays (the Model). Rather than letting the View code directly manipulate the Model&#039;s data, the MVC pattern introduces a third party known as the Controller.&lt;p&gt;&lt;a href=&quot;http://philmccarthy.sys-con.com/node/351862&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 19 Apr 2007 08:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://philmccarthy.sys-con.com/node/351862</guid>
 <comments>http://philmccarthy.sys-con.com/node/351862#feedback</comments>
</item>
</channel>
</rss>
