<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Sean's Software Blog</title>
	<atom:link href="http://seanoc.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://seanoc.wordpress.com</link>
	<description>Some words from a simple web develper.</description>
	<lastBuildDate>Tue, 26 May 2009 02:21:15 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<image>
		<url>http://www.gravatar.com/blavatar/3cb55596e4ce7d1cb923028fab7a4548?s=96&#038;d=http://s.wordpress.com/i/buttonw-com.png</url>
		<title>Sean's Software Blog</title>
		<link>http://seanoc.wordpress.com</link>
	</image>
			<item>
		<title>Solango Tips and Gotchas</title>
		<link>http://seanoc.wordpress.com/2009/05/25/solango-gotchas/</link>
		<comments>http://seanoc.wordpress.com/2009/05/25/solango-gotchas/#comments</comments>
		<pubDate>Tue, 26 May 2009 02:21:15 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[Django]]></category>
		<category><![CDATA[Guides/How-Tos]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[Solr]]></category>

		<guid isPermaLink="false">http://seanoc.wordpress.com/?p=64</guid>
		<description><![CDATA[For the last week or so I've been wrapping my brain around Solr and Solango.  The whole time that I've been doing this I've had the feeling that they can do awesome, powerful things but they're documentation is so poor that I couldn't figure anything out beyond the basic examples.  Ultimately I had to dig through a bunch of code and do some experimentation.  Now that I've finally figured out how to do what I've been trying to do and have wrapped my brain around some of the trickier bits I'm going to share some of the gotchas and solutions I've found.<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=64&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2009/05/25/solango-gotchas/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>sPaste Update</title>
		<link>http://seanoc.wordpress.com/2009/02/24/spaste-update/</link>
		<comments>http://seanoc.wordpress.com/2009/02/24/spaste-update/#comments</comments>
		<pubDate>Tue, 24 Feb 2009 06:08:05 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[Django]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Personal-Projects]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[sPaste]]></category>

		<guid isPermaLink="false">http://seanoc.wordpress.com/?p=60</guid>
		<description><![CDATA[After a bit of a break, there is now a bit of new functionality in sPaste.  Now when creating a snippet users can select a date and a number of views, after which the snippet will self-destruct.  This update adds a great extra layer of security by only allowing information to exist in sPaste just [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=60&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2009/02/24/spaste-update/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>sPaste&#124;source &#8211; a secure, open source, pastebin</title>
		<link>http://seanoc.wordpress.com/2008/10/31/spastesource-a-secure-open-source-pastebin/</link>
		<comments>http://seanoc.wordpress.com/2008/10/31/spastesource-a-secure-open-source-pastebin/#comments</comments>
		<pubDate>Fri, 31 Oct 2008 05:52:40 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[Django]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Python]]></category>

		<guid isPermaLink="false">http://seanoc.wordpress.com/?p=58</guid>
		<description><![CDATA[A few months ago, I found myself with a frequent itch at work.  Often I needed to send sensitive information such as access credentials to co-workers and clients.  Obviously email isn&#8217;t an acceptable way to send this information, but anything much more complex than email overly frustrates who ever I am sending information to.
My solution [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=58&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2008/10/31/spastesource-a-secure-open-source-pastebin/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>Quick Django Trick</title>
		<link>http://seanoc.wordpress.com/2008/09/03/quick-django-trick/</link>
		<comments>http://seanoc.wordpress.com/2008/09/03/quick-django-trick/#comments</comments>
		<pubDate>Thu, 04 Sep 2008 04:37:02 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[Django]]></category>
		<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[Guides/How-Tos]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Python]]></category>

		<guid isPermaLink="false">http://seanoc.wordpress.com/?p=53</guid>
		<description><![CDATA[Recently while playing around with a Django model in the always awesome iPython shell I discoved a neat feature of the Django ORM.  It&#8217;s basically a way to get the id of a related object without actually triggering a query to get all of the related object&#8217;s data.
Frequently when working with a model which has [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=53&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2008/09/03/quick-django-trick/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>Annoucning sPaste.com</title>
		<link>http://seanoc.wordpress.com/2008/07/31/annoucning-spastecom/</link>
		<comments>http://seanoc.wordpress.com/2008/07/31/annoucning-spastecom/#comments</comments>
		<pubDate>Thu, 31 Jul 2008 05:37:48 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[Django]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[jquery]]></category>
		<category><![CDATA[projects]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[sPaste]]></category>
		<category><![CDATA[tools]]></category>

		<guid isPermaLink="false">http://seanoc.wordpress.com/?p=31</guid>
		<description><![CDATA[Tonight I am officially launching my new side project,  sPaste.com!  sPaste is a simple tool to help you quickly and securely send small snippets of data around the web.  As usual, the site is written entirely in Django on the server side and jQuery on the client side.  At the moment it is little more [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=31&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2008/07/31/annoucning-spastecom/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>Update to django-ae-utils</title>
		<link>http://seanoc.wordpress.com/2008/05/07/update-to-django-ae-utils/</link>
		<comments>http://seanoc.wordpress.com/2008/05/07/update-to-django-ae-utils/#comments</comments>
		<pubDate>Wed, 07 May 2008 20:43:19 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[App Engine]]></category>
		<category><![CDATA[Django]]></category>
		<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[django-ae-utils]]></category>

		<guid isPermaLink="false">http://seanoc.com/?p=27</guid>
		<description><![CDATA[I&#8217;ve been hanging out at the NYC App Engine Hackathon today and I&#8217;ve had some time to work on django-ae-utils.  Accordingly I&#8217;ve just posted an update to django-ae-utils.  This update includes a User model which uses the App Engine datastore as a backend, as well as a few generic views for working with the model.
Check [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=30&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2008/05/07/update-to-django-ae-utils/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>Introducing django-ae-utils</title>
		<link>http://seanoc.wordpress.com/2008/04/21/introducing-django-ae-utils/</link>
		<comments>http://seanoc.wordpress.com/2008/04/21/introducing-django-ae-utils/#comments</comments>
		<pubDate>Mon, 21 Apr 2008 07:06:45 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[App Engine]]></category>
		<category><![CDATA[Django]]></category>
		<category><![CDATA[Frameworks]]></category>
		<category><![CDATA[General]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Open Source]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[django-ae-utils]]></category>

		<guid isPermaLink="false">http://seanoc.com/?p=25</guid>
		<description><![CDATA[Recently I&#8217;ve started to play around with using Django on Google&#8217;s new App Engine.  As mentioned by many others at this point, Django technically runs on App Engine but there are significant parts which do not.  Accordingly I&#8217;ve started to write some code to replace or supplement the holes left in Django by App Engine.  [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=29&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2008/04/21/introducing-django-ae-utils/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>Google Launches App Engine</title>
		<link>http://seanoc.wordpress.com/2008/04/08/google-launches-app-engine/</link>
		<comments>http://seanoc.wordpress.com/2008/04/08/google-launches-app-engine/#comments</comments>
		<pubDate>Tue, 08 Apr 2008 05:27:30 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[Django]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Hosting]]></category>
		<category><![CDATA[Python]]></category>
		<category><![CDATA[Web Services]]></category>

		<guid isPermaLink="false">http://seanoc.com/archive/2008/04/08/google-launches-app-engine/</guid>
		<description><![CDATA[Google just launched a new platform called App Engine.  Basically it allows you to run your web application on Google&#8217;s servers using much of their main infrastructure such as BigTable and GFS.  The best part is, you write App Engine apps in Python and they include Django out of the box!  Mike Arrington has a video of Guido Van [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=28&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2008/04/08/google-launches-app-engine/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>Working around MySQL&#8217;s horrible &#8220;ORDER BY rand()&#8221; in Django</title>
		<link>http://seanoc.wordpress.com/2008/01/27/working-around-mysqls-horrible-order-by-rand-in-django/</link>
		<comments>http://seanoc.wordpress.com/2008/01/27/working-around-mysqls-horrible-order-by-rand-in-django/#comments</comments>
		<pubDate>Sun, 27 Jan 2008 06:56:05 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[Databases]]></category>
		<category><![CDATA[Django]]></category>
		<category><![CDATA[Guides/How-Tos]]></category>
		<category><![CDATA[MySQL]]></category>
		<category><![CDATA[Python]]></category>

		<guid isPermaLink="false">http://seanoc.com/archive/2008/01/27/working-around-mysqls-horrible-order-by-rand-in-django/</guid>
		<description><![CDATA[Recently I&#8217;ve been working on a web 2.0ish community site written in Django.   As is frequently the case with such sites I often need to create lists or collections of psuedo-randomly selected items.   For example on a user&#8217;s profile page there may be a box showing a few of the user&#8217;s [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=27&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2008/01/27/working-around-mysqls-horrible-order-by-rand-in-django/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
		<item>
		<title>Django Gotcha &#8211; Inline Foriegn Key Fields</title>
		<link>http://seanoc.wordpress.com/2008/01/21/django-gotcha-inline-foriegn-key-fields/</link>
		<comments>http://seanoc.wordpress.com/2008/01/21/django-gotcha-inline-foriegn-key-fields/#comments</comments>
		<pubDate>Mon, 21 Jan 2008 04:31:45 +0000</pubDate>
		<dc:creator>seanoc</dc:creator>
				<category><![CDATA[Django]]></category>

		<guid isPermaLink="false">http://seanoc.com/archive/2008/01/21/django-gotcha-inline-foriegn-key-fields/</guid>
		<description><![CDATA[Working on a project recently, I came across an interesting gotcha in using inline foreign keys in the Django admin.  Apparently the objects described by the inline fields are saved after the parent object is saved.  This becomes important if you try and do anything with the child objects as part of the parent object&#8217;s [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=seanoc.wordpress.com&blog=4121282&post=26&subd=seanoc&ref=&feed=1" />]]></description>
		<wfw:commentRss>http://seanoc.wordpress.com/2008/01/21/django-gotcha-inline-foriegn-key-fields/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
	
		<media:content url="http://1.gravatar.com/avatar/174cf6e6ea7ab41d54c73feb8670148b?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">seanoc</media:title>
		</media:content>
	</item>
	</channel>
</rss>