<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>fastr on chrismoos</title>
    <link>/tags/fastr/</link>
    <description>Recent content in fastr on chrismoos</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2020 Chris Moos</copyright>
    <lastBuildDate>Mon, 21 Jun 2010 21:17:18 +0000</lastBuildDate><atom:link href="/tags/fastr/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AsyncRecord: Non-blocking database access for Ruby</title>
      <link>/2010/06/21/asyncrecord-non-blocking-database-access-for-ruby/</link>
      <pubDate>Mon, 21 Jun 2010 21:17:18 +0000</pubDate>
      
      <guid>/2010/06/21/asyncrecord-non-blocking-database-access-for-ruby/</guid>
      <description>Two weeks ago I developed my first event-driven web framework for Ruby, Fastr. It helped me understand why running a web framework in an event loop is so natural.
As I continued to tackle more features in Fastr, it was time to tackle persistence &amp;ndash; notably, database access.
AsyncRecord is/will be an ORM, similar to ActiveRecord &amp;ndash; with one major difference &amp;ndash; it doesn&amp;rsquo;t block. AsyncRecord currently uses em-mysql to access a MySQL database.</description>
    </item>
    
  </channel>
</rss>
