NAME bj
SYNOPSIS bj (migration_code|generate_migration|migrate|setup|run|submit|list| set>config>pid) [options]+
DESCRIPTION
Not exactly the best name... 
. not really. spawn, backgrounddrb, and bj all serve very different purposes. for better or worse the rail conversation seems to be happening over here
http://groups.google.com/group/ruby-talk-google/browse_frm/thread/144e9b3644ffe88e#38b99ec30098b956
join in! 
Hey Ara, sorry to post a ticket like this... rubyforge has been down for me all day (local internet issues, no clue...) I had a few issues using the plugin I wanted to mention before I forgot.
One is that freezing in the gems doesn't really work because they try to load each other. The 'main' gem has tries to load the 'attributes' gem, even if its frozen inside the bj plugin. Not a big deal since I can just load the gems...
The more important issue is that your definition of #instance_methods differs from the ruby core api (which includes an extra argument). This breaks gems like aws-s3. Here's a patch (Parked at Loopia), but I'm not sure if it'll break for users on older versions of ruby. At any rate, just thought I'd let you know.
Thanks for the library though. It seems like it'll work a lot better than my own job queue service...
> NAME > bj
Hey Ara, sorry to post a ticket like this... rubyforge has been down for me all day (local internet issues, no clue...) I had a few issues using the plugin I wanted to mention before I forgot.
thanks for tip rick!
One is that freezing in the gems doesn't really work because they try to load each other. The 'main' gem has tries to load the 'attributes' gem, even if its frozen inside the bj plugin. Not a big deal since I can just load the gems...
yeah this bums me out and i haven't found a good work around. i'm playing with setting GEM_PATH now, but even that doesn't really seem to work ;-(
The more important issue is that your definition of #instance_methods differs from the ruby core api (which includes an extra argument). This breaks gems like aws-s3. Here's a patch (Parked at Loopia), but I'm not sure if it'll break for users on older versions of ruby. At any rate, just thought I'd let you know.
thanks - that, and bunch of other stuff, is fixed in the new version - due out today or tomorrow.
Thanks for the library though. It seems like it'll work a lot better than my own job queue service...
glad to hear you are liking it!
-a