<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="http://www.majordojo.com/projects/FeedManager/atom.xsl" type="text/xsl" media="screen"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.majordojo.com/2009/12/media-manager-works-with-amazon-again.php" />
  <link rel="self" type="application/atom+xml" href="http://www.majordojo.com/2009/12/media-manager-works-with-amazon-again.php" />
  <id>tag:www.majordojo.com,2010://3/tag:www.majordojo.com,2009://3.14991-</id>
  <updated></updated>
  <title>Comments for Media Manager works with Amazon. Again.</title>
  <subtitle>A blog about Movable Type, technology, geek-dom, science-fiction and yes, sometimes my personal life.</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.261</generator>
  <entry>
    <id>tag:www.majordojo.com,2009://3.14991</id>
    <link rel="alternate" type="text/html" href="http://www.majordojo.com/2009/12/media-manager-works-with-amazon-again.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.majordojo.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=3/entry_id=14991" title="Media Manager works with Amazon. Again." />
    <published>2009-12-08T19:37:15Z</published>
    <updated>2009-12-08T20:18:55Z</updated>
    <title>Media Manager works with Amazon. Again.</title>
    <summary>Not too long ago Amazon made some important changes to its API to improve security, but this change had the unfortunate result of breaking Media Manager. My knee-jerk reaction was to just go into my code and implement the API...</summary>
    <author>
      <name>Byrne</name>
      <uri>http://www.majordojo.com/</uri>
    </author>
    
    <category term="Announcements" />
    
    <category term="Movable Type" />
    
    <category term="Personal Projects" />
    
    <content type="html" xml:lang="en" xml:base="http://www.majordojo.com/">
      <![CDATA[<p>Not too long ago Amazon made some important changes to its API to improve security, but this change had <a href="http://www.majordojo.com/2009/09/media-manager-users-thank-amazon.php">the unfortunate result of breaking Media Manager</a>. My knee-jerk reaction was to just go into my code and implement the API change directly in my custom built Amazon API library -- because hey, it would fix the problem and allow me to go about my day. But working on <a href="http://openmelody.org">Melody</a> has been a reminder to me about how important it is to drop proprietary code in favor of third party libraries when they emerge. It is not always the <em>easy</em> thing to do, because it often requires a huge effort to rewire your code to a new library, but in most cases it is the <em>right</em> thing to do because in the long run it will:</p>

<ul>
<li>Consolidate development around a library that more people will benefit from.</li>
<li>Bring more features to your users faster.</li>
<li>Allow you to leverage documentation written and maintained by someone else.</li>
<li>Increase the size of your support community.</li>
</ul>

<p>And that is what I did with Media Manager. I dropped all of my old proprietary Amazon API code in favor of a widely used, well supported CPAN module called <a href="http://search.cpan.org/~boumenot/Net-Amazon-0.59/lib/Net/Amazon.pm">Net::Amazon</a>. In the process I dramatically simplified my code base, I incorporated more features that have emerged from Amazon's API since I initially wrote Media Manager, and made the framework easier to extend and use. All in all, it is proving to be a <em>great</em> change for the plugin that brings <em>more features and capabilities</em> to Media Manager users.</p>

<p>However, this change may also mean changes for its users. For a lot of Media Manager users, this new version may mean that your template code will no longer work. This change which breaks backwards compability was unfortunate, but to a great extent unavoidable, especially if I wanted to maximize the end-user benefits for shifting to Net::Amazon. So if you are an existing user of Media Manager and are anxious to restore interoperability with Amazon, then please consult Media Manager's <a href="http://www.majordojo.com/projects/movable-type/media-manager/documentation/">new documentation with its many template code samples</a> to see what changes you might need to update your blog's templates.</p>

<p>You can <a href="http://github.com/byrnereese/mt-plugin-mediamanager/downloads">download Media Manager 2.1 from github</a>, and <a href="http://majordojo.lighthouseapp.com/projects/36618-media-manager/tickets">file support tickets and bug reports in lighthouse</a>. Please, if you have problems, let me know so that I fix them as soon as possible. </p>
]]>
      

    </content>
  </entry>

</feed>
