<?xml version="1.0" encoding="UTF-8"?>

    <feed xmlns="http://www.w3.org/2005/Atom">
        <title>tummy.com, ltd.</title>
        <subtitle>Your Linux Data Center Experts</subtitle>
        <link rel="alternate" href="http://www.tummy.com/" />
        <link rel="self" href="http://www.tummy.com/feed.xml" type="application/atom+xml" />
        <id>http://www.tummy.com/</id>
        <updated>2013-06-13T00:15:05Z</updated>
        
        <author>
            <name>tummy.com, ltd.</name>
            <email>webmaster@tummy.com</email>
            <uri>http://www.tummy.com/</uri>
        </author>
        
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
        
           
            <entry>
                <title>Interesting read on request versus response rate limiting.</title>
                <link rel="alternate" href="http://www.tummy.com/blogs/2013/01/11/interesting-read-on-request-versus-response-rate-limiting/" type="text/html" />
                <id>http://www.tummy.com/blogs/2013/01/11/interesting-read-on-request-versus-response-rate-limiting/</id>
                <updated>2013-01-11T12:28:00Z</updated>
                
                <summary type="html">We&amp;#39;ve recently been the reflection point in a DNS-based reflection+amplification attack. We implemented some rate limiting to prevent it, and as part of my research on this topic I found this discussion to be fascinating. In particular, the trade-offs between request rate limiting and response rate limiting... It&amp;#39;s about half way down in &lt;a href=&#34;http://comments.gmane.org/gmane.network.dns.operations/1403&#34;&gt;this dns-operations thread on &amp;quot;DNS ANY from Amazon&amp;quot;&lt;/a&gt;.</summary>
                <content type="html">&lt;p&gt;We&amp;#39;ve recently been the reflection point in a DNS-based reflection+amplification attack. We implemented some rate limiting to prevent it, and as part of my research on this topic I found this discussion to be fascinating. In particular, the trade-offs between request rate limiting and response rate limiting... It&amp;#39;s about half way down in &lt;a href=&#34;http://comments.gmane.org/gmane.network.dns.operations/1403&#34;&gt;this dns-operations thread on &amp;quot;DNS ANY from Amazon&amp;quot;&lt;/a&gt;.&lt;/p&gt;
</content>
            </entry>
           
        
           
            <entry>
                <title>SVN directories</title>
                <link rel="alternate" href="http://www.tummy.com/blogs/2012/12/21/svn-directories/" type="text/html" />
                <id>http://www.tummy.com/blogs/2012/12/21/svn-directories/</id>
                <updated>2012-12-21T14:22:00Z</updated>
                
                <summary type="html">Just a note on something I&amp;#39;ve noticed in Ubuntu Quantal... It includes Subversion version 1.7.5, which has this compelling feature: The .svn directories have been merged into a single directory at the top level of your checkout. So no longer are the subdirectories littered with .svn directories. Makes script and find commands of sub-sections of the repository easier.</summary>
                <content type="html">&lt;p&gt;Just a note on something I&amp;#39;ve noticed in Ubuntu Quantal... It includes Subversion version 1.7.5, which has this compelling feature: The .svn directories have been merged into a single directory at the top level of your checkout. So no longer are the subdirectories littered with .svn directories. Makes script and find commands of sub-sections of the repository easier.&lt;/p&gt;
</content>
            </entry>
           
        
           
            <entry>
                <title>Skeleton for testing Python code.</title>
                <link rel="alternate" href="http://www.tummy.com/blogs/2012/12/14/skeleton-for-testing-python-code/" type="text/html" />
                <id>http://www.tummy.com/blogs/2012/12/14/skeleton-for-testing-python-code/</id>
                <updated>2012-12-14T23:18:00Z</updated>
                
                <summary type="html">Thanks to Bill Tucker and 2011&amp;#39;s &lt;a href=&#34;http://coderetreat.org/&#34;&gt;Code Retreat&lt;/a&gt; that he put on, I&amp;#39;ve become quite the convert to testing. I knew I should be doing it, but I never found the time to become really comfortable with them until Code Retreat. </summary>
                <content type="html">&lt;p&gt;Thanks to Bill Tucker and 2011&amp;#39;s &lt;a href=&#34;http://coderetreat.org/&#34;&gt;Code Retreat&lt;/a&gt; that he put on, I&amp;#39;ve become quite the convert to testing. I knew I should be doing it, but I never found the time to become really comfortable with them until Code Retreat. &lt;/p&gt;

&lt;p&gt;However, especially when I was starting, I found I really needed some examples and wanted some boilerplate I could just drop in place. At the Code Retreat I had just recently come back across an entry I made on my personal Wiki that had some examples. Since then I&amp;#39;ve expanded on them and today I included some examples of testing Bottle web applications (I still totally love Bottle by the way). &lt;/p&gt;

&lt;p&gt;I&amp;#39;ve create a github account that has these examples and related code such as a &amp;quot;Makefile&amp;quot; which automatically runs the test. You can find it at &lt;a href=&#34;https://github.com/linsomniac/python-unittest-skeleton&#34;&gt;https://github.com/linsomniac/python-unittest-skeleton&lt;/a&gt;. I hope you find it as useful as I have.&lt;/p&gt;
</content>
            </entry>
           
        
    </feed>
