<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/">

  <channel rdf:about="http://www.electricsenator.net:80/">
    <title>Electric Senator</title>
    <link>http://www.electricsenator.net:80/</link>
    <description>Artificial Intelligence and Code</description>
    <items>
      <rdf:Seq>
        
        <rdf:li resource="http://www.electricsenator.net:80/2009/10/20/1256057880000.html" />
        
        <rdf:li resource="http://www.electricsenator.net:80/2009/10/17/1255796820000.html" />
        
        <rdf:li resource="http://www.electricsenator.net:80/2009/10/04/1254633530109.html" />
        
        <rdf:li resource="http://www.electricsenator.net:80/2009/10/03/1254623760000.html" />
        
        <rdf:li resource="http://www.electricsenator.net:80/2009/10/03/1254618530821.html" />
        
        <rdf:li resource="http://www.electricsenator.net:80/2009/09/25/1253924425381.html" />
        
      </rdf:Seq>
    </items>
  </channel>

  
  <item rdf:about="http://www.electricsenator.net:80/2009/10/20/1256057880000.html">
    <title>PostgreSQL and Grails</title>
    <link>http://www.electricsenator.net:80/2009/10/20/1256057880000.html</link>
    
      
      
        <description>
          I&#039;ve been using grails for web applications for a while and my preferred database for these applications is &lt;a href=&#034;http://www.postgresql.org/&#034;&gt;PostgreSQL&lt;/a&gt;.  Unfortunately recently I&#039;ve run into a number of bugs when using &lt;a href=&#034;http://cwiki.apache.org/SHIRO/&#034;&gt;Apache Shiro&lt;/a&gt; for security.&lt;p&gt;&lt;a href=&#034;http://www.electricsenator.net:80/2009/10/20/1256057880000.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
  </item>
  
  <item rdf:about="http://www.electricsenator.net:80/2009/10/17/1255796820000.html">
    <title>Tomcat and JNDI</title>
    <link>http://www.electricsenator.net:80/2009/10/17/1255796820000.html</link>
    
      
      
        <description>
          &lt;p&gt;
JNDI allows your application to look up resources provided to it by the server on which it is running.  This article will show you how to provide databases and a mail server to your web applications under Tomcat.
&lt;/p&gt;&lt;p&gt;&lt;a href=&#034;http://www.electricsenator.net:80/2009/10/17/1255796820000.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
  </item>
  
  <item rdf:about="http://www.electricsenator.net:80/2009/10/04/1254633530109.html">
    <title>SysV Shared Memory Under Unix</title>
    <link>http://www.electricsenator.net:80/2009/10/04/1254633530109.html</link>
    
      
      
        <description>
          &lt;p&gt;An old blog that needed a new home.&lt;/p&gt;

&lt;p&gt;Shared memory is the fastest method of inter-process communication,
    IPC, available to a Unix process. It allows multiple processes to use
    the same data structures and regulate access to them based on rules
    the processes define themselves. System V shared memory is faster than
    shared memory mapping on some Unix operating systems and is still more
    prevalent than POSIX shared memory. In order to demonstrate how to use
    shared memory we develop a simple client server application that takes
    advantage of SysV shared memory and semaphores.&lt;/p&gt;&lt;p&gt;&lt;a href=&#034;http://www.electricsenator.net:80/2009/10/04/1254633530109.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
  </item>
  
  <item rdf:about="http://www.electricsenator.net:80/2009/10/03/1254623760000.html">
    <title>Blog Refocused</title>
    <link>http://www.electricsenator.net:80/2009/10/03/1254623760000.html</link>
    
      
      
        <description>
          &lt;p&gt;
I&#039;ve decided for various reasons to focus this blog only on software development, artificial intelligence and related issues.  The other topics that took up most of the space here will not be back, but I may post them at a different location in the future. 
&lt;/p&gt;

&lt;p&gt;
I&#039;m going to try to document the technical projects I&#039;m engaged in here, without distractions from other topics of less value to my readers.  If you are looking for a post that you can no longer find, feel free to send me a note and I&#039;ll get the information to you.    
&lt;/p&gt;&lt;p&gt;&lt;a href=&#034;http://www.electricsenator.net:80/2009/10/03/1254623760000.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
  </item>
  
  <item rdf:about="http://www.electricsenator.net:80/2009/10/03/1254618530821.html">
    <title>Installing A Continuous Integration Server</title>
    <link>http://www.electricsenator.net:80/2009/10/03/1254618530821.html</link>
    
      
      
        <description>
          &lt;p&gt;
A friend of mine convinced me that I should at least give continuous integration
servers a try to see if they might streamline my development process.  I thought
that a CI server might be a wonderful way to aid in communication with my 
clients.  They would be able to see that status of work as it is being 
developed.  Knowing that the customer is able to see not only the final version
of the code, but every intermediate version and it status in testing can only
improve the quality of the released product.  
&lt;/p&gt;&lt;p&gt;&lt;a href=&#034;http://www.electricsenator.net:80/2009/10/03/1254618530821.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
  </item>
  
  <item rdf:about="http://www.electricsenator.net:80/2009/09/25/1253924425381.html">
    <title>Google App Engine for Java Developers</title>
    <link>http://www.electricsenator.net:80/2009/09/25/1253924425381.html</link>
    
      
      
        <description>
          &lt;p&gt;
Google&#039;s App Engine is based on a great idea, cloud computing but without having to provision individual servers to host your application.  Most people deploying to the cloud don&#039;t really care about how many servers are handling their app at any given time, they just want it available whenever a customer needs it.  They also don&#039;t really want to spend their time optimizing database performance, or caching performance, or any of the details that are best left up to experts like those at Google.  
&lt;/p&gt;&lt;p&gt;&lt;a href=&#034;http://www.electricsenator.net:80/2009/09/25/1253924425381.html&#034;&gt;Read more...&lt;/a&gt;&lt;/p&gt;
        </description>
      
    
  </item>
  

</rdf:RDF>
