search for: drbfire

Hi, I''m using drbfire to send a "DRbUndumped" ActiveRecord object from the server to the client, through an ADSL line of 4Mbits/s download, and 600Kbits/s upload. I was afraid there would be too many round-trips between the client and the server, and unfortunately this is true: Server code: ------------ #!/...

I''m having trouble getting backgroundrb up and running in a production environment. Here''s my backgroundrb.yml: --- port: "22222" timer_sleep: 60 load_rails: true environment: production host: XXX.XX.XXX.50 database_yml: config/database.yml acl: deny: all allow: localhost 127.0.0.1 XXX.XX.XXX.51 order: deny,allow I start BackgroundRB from XXX.XX.XXX.50 with

Hi Everyone, I figured out this weekend that Ruby''s Thread implementation causes the Ruby/Event binding I wrote to completely stall and go dead. After reviewing the Ruby source and watching several strace runs, it''s clear that the Ruby Thread implementation uses select in a way that--while not being bad--just isn''t compatible with libevent. The second a thread is