<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 23 May 2013 20:54:05 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[NPR.org: Building the Ingest System]]></title>
      <guid>http://www.phpdeveloper.org/news/14576</guid>
      <link>http://www.phpdeveloper.org/news/14576</link>
      <description><![CDATA[<p>
On NPR.org there's <a href="http://www.npr.org/blogs/inside/2010/04/22/126205655/building-the-ingest-system">a recent article</a> talking about their <a href="http://www.npr.org/blogs/inside/2010/03/24/125120202/API-Release%E2%80%94-Station-Content%E2%80%94Blogs-and-Search">Ingest system</a> they've built that allows partner stations to pull and distribute their content.
</p>
<blockquote>
The Ingest System currently accepts stories in two XML data formats. We accept a limited subset of <a href="http://www.npr.org/api/outputReference.php">NPRML</a> - our own home-grown way of expressing story content in XML.  We also accept RSS with MediaRSS and NPRML extensions for audio and images and other resources. [...] While implementing the Ingest System, we faced an interesting technical challenge.  Our APIs, including the components we use to authenticate API access, are written in PHP, while our content management system (CMS) is written in Java. 
</blockquote>
<p>
The article describes how their API system works, pulling together XML content, serialized JSON messaging and an authentication component to push and pull data to and from their Java-based CMS - complete with <a href="http://media.npr.org/assets/img/2010/05/03/Ingest_custom.jpg?t=1272907556&s=2">a diagram</a> laying out the whole process.
</p>]]></description>
      <pubDate>Fri, 28 May 2010 12:10:57 -0500</pubDate>
    </item>
  </channel>
</rss>
