ruote

Here are my slides for the “edo cabinet” talk at the RubyKaigi2009. I presented about Ruby-FFI, Tokyo Cabinet|Tyrant and then rufus-tokyo and Rufus::Edo. These are just slides, here is the english transcript of the actual talk.   Many thanks to the ... [More] RubyKaigi team for organizing this great event ! Special kudos to Leonard Chin for the on-the-fly translations, throughout [...] [Less]

Just released rufus-tokyo 1.0.0 This is mostly a “cleanup” release (spec reorg, to_s enforcement on key and values, and dropped backward compatibility with older TC/TT releases). Hence the 1.0.0. There are new features though : * Matthew King helped ... [More] me add process method for table queries. * Jeremy Hinegardner did an initial contribution on the front FFI / Tokyo [...] [Less]

This post is intended for Ruby developers. The idea for it came after numerous discussions with fellow programmers about state machines and workflow engines. What motivates me for posting is the publication of the 3rd issue of the excellent Rails ... [More] Magazine. It contains an article named “Workflow solutions with AASM”. At first a word of warning, [...] [Less]

With the initial releases of rufus-tokyo, I happily cut corners and went with C strings (ending with NUL). This isn’t optimal, often you need to store binary data as the value, the resulting ’string’ contains NUL characters and values get truncated at restitution. I was working around that with Base64 encoding. Fine, the perf cost isn’t [...]

This blog is turning into a release gallery. Anyway. Just released rufus-scheduler 2.0. It’s a complete rewrite. The only new “feature” is an EventMachine mode. The plain scheduler uses a thread waking up every 0.330s (by default) to check for jobs ... [More] to trigger, while the em-based scheduler uses an EventMachine timer. Other flavour for the core loop are [...] [Less]

rufus-decision is a small ruby gem for ‘running decision tables’. Decision tables are useful for mapping conditions to actions. This example decision table considers two conditions : ‘topic’ and ‘region’ (I tend to call them ‘inputs’). Certain ... [More] combinations of condition yield one or more output value. In the example, when the topic is about finance and [...] [Less]

Just released version 0.1.12 of rufus-tokyo, a Ruby library for accessing Tokyo Cabinet and Tokyo Tyrant (via FFI or via the Ruby classes provided with the Tokyo products). Tokyo Tyrant, once successfully compiled with –enable-lua, is open to lots of interesting usages. In his last post on the Mixi dev blog, the author of Tokyo Cabinet / [...]

This doesn’t deserve a gem. It’s just a plain file, so it’s packaged as a gist. It’s inspired by Rails’ rake rails:freeze:gems but I made it for my non-rails stuff. jmettraux@sanma ~/tmp/test $ ruby frigo.rb dm-migrations . created dir vendor .. ... [More] from http://gems.rubyforge.org/ got dm-migrations-0.9.10 .. from http://gems.rubyforge.org/ got dm-core-0.9.10 .. from http://gems.rubyforge.org/ got data_objects-0.9.11 .. [...] [Less]

Just released rufus-lua 1.0 There are two main new features : lua garbage collection control (thanks Alain) and the possibility to bind Ruby blocks as Lua functions. Rufus-lua is available via sudo gem install rufus-lua  

Just released rufus-tokyo 0.1.10. It supports the new setlimit method in Tokyo Cabinet 1.4.10 tables and Tokyo Tyrant 1.1.17 tables. (I put up a piece of documentation on how to install TC and TT at http://openwferu.rubyforge.org/tokyo.html) What’s ... [More] the deal with this setlimit method ? Well, it’s an improvement over setmax which only accepted a count parameter. require 'rubygems' require [...] [Less]