batsir

batsir

Batsir uses so called stages to define operation queues. These operation queues consist of several operations that will be executed one after the other. Each stage is defined by its name and the queue on which it will listen. Once a message is received on the queue, it is dispatched to a worker in a seperate thread that will pass the message to each operation in the operation queue. Operation queues can have 4 different operations, 1 common operation type, and 3 special purpose operations: retrieval operations (which are always executed before all other operations), persistence operations (which are always executed after the common operations, but before the notification operations) and notification operations (which will always be executed last) This makes it possible to create chains of stages to perform tasks that depend on each other, but otherwise have a low coupling

Rubygem batsir

Total Downloads
1768
Releases
3
Current Version
0.3.7.1
Released
2013-10-24 00:00:00 UTC
First Release
2012-06-28 00:00:00 UTC
Depends on following gems
Depending Gems
0

Github jwkoelewijn/batsir

Watchers
55
Forks
5
Development activity
Less active
Last commit
2014-01-31 09:20:14 UTC
First commit
Top contributors
Contributors
4
Issues
Wiki pages

Resources

There are no resources yet, be the first to submit one!

Comments

There are no comments yet, be the first to write one!

Post a comment

Markdown supported
or
×

In order to continue, you must be signed in using your Github account.

If you're signing in using this account for the first time Github will ask for your permission to give access to your public user data to the Ruby Toolbox.

Although the Github Authorization page does not mention it, the request includes read-only access to your verified email address (user:email OAuth scope). This is neccessary so there's a way to notify you about comments, information about your accepted project edits and the like. You can review your notification settings on your account page once you're signed in.