<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
<channel>
<title>Keith's Web Blog RSS Feed</title>
<language>en-us</language>
<link>http://www.keithwatanabe.net/index.php</link>
<description>Keith Watanabe's Website</description>
<item>
<title>Zend Framework and Web Services</title>
<link>http://www.keithwatanabe.net/blogs/2008/4/5/31948c386812b988bc4ac7302a341961.html</link>
<description><![CDATA[I've been pretty harsh against the Zend Framework in terms as it is far too loosely coupled component based system.  However, I've utterly fallen in love with the way the Zend Framework handles Web Services.  At the moment, I've embarked on a home project for utilizing Amazon's Web services.  If I had to parse the XML by myself, I think I would go crazy.  Here's where you really want to have a thoroughly tested mechanism to handle the heavy duty work.<br />
<br />
The Zend Framework makes the item search capabilities quite easy.  You just need a web service key to be able to search against Amazon's massive item database.  The real trick in all of this is figuring out how to tune your searches against Amazon as well as caching the results.  Once you get that working, it's quite smooth sailing.<br />
<br />
The only problem i see against this really isn't an issue of the Zend Framework, but a problem with Amazon's policy of only allowing a single query per IP address per second.  While I understand the reason, I hope one day that they'll eventually lower this requirement.  At least the number of queries is no longer monitored, unlike other web services.]]></description>
<pubDate>Sat, 05 Apr 2008 13:26:05 -0600</pubDate>
<guid>http://www.keithwatanabe.net/blogs/2008/4/5/31948c386812b988bc4ac7302a341961.html</guid>
</item>
</channel>
</rss>
