search for: opensoul

I have a new blog post about some thoughts that I''ve had as I''ve been using rspec lately. I would love to hear your thoughts: http://opensoul.org/2007/6/20/rspec-is-getting-too-intimate-with- my-code Brandon

I was just curious if anyone noticed any significant performance improvements using fastthread (or Ruby 1.8.6) with BackgrounDRb Brandon -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 186 bytes Desc: This is a digitally signed message part Url :

Hello there, I need to build an audit trail system for an application. So far I have been looking at acts_as_versioned and acts_as_versioned_association plugins. I am having troubles getting the second one to work. Any how, do you have any suggestions about how to build a robust audit trail? Thanks, Roland -- Posted via http://www.ruby-forum.com/.

I came across this awesome plugin used for auditing models. This is an ActiveRecord extension. However I was wondering if I could tweak it a little to make it work for ActiveResource. In case you haven''t heard about acts_as_audited plugin, here is the link to check it out. http://opensoul.org/2006/07/21/acts_as_audited Is there anyone who has experience in similar context? Please help! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send emai...

In Ruby, classes are never closed: you can always add methods to an existing class. This applies to the classes you write as well as the standard, built-in classes. All you have to do is open up a class definition for an existing class, and the new contents you specify will be added to whatever''s there. In the same regard, if module is used with the name of a pre-existing module that

Having used JUnit and Test::Unit, I''m quite used to having the ability to insert a failure message, which helps when tests fail. For instance, the example RSpec that is generated for a model class specifies that the model class is valid. Assuming this were supposed to be true, and it failed, I''ve now got to duplicate the code in the test in order to find out why it

Hi Folks, BackgrounDRb is a Ruby job server and scheduler. Its main intent is to be used with Ruby on Rails applications for offloading long-running tasks. Since a Rails application blocks while serving a request it is best to move long-running tasks off into a background process that is divorced from http request/response cycle. This new release of BackgrounDRb is also modular and can be used

I just started using BackgrounDRb this week and am really impressed. Good work Ezra and everyone else that has contributed. I''m writing a web app to subscribe to feeds with video enclosures and then play them in a flash player, or export them to MythTV or something like it. I''m using BackgrounDRb for the downloading and video processing. The docs mention that the

We''ve made quite a few contributions in our facebooker fork (http://github.com/collectiveidea/facebooker ), but unfortunately, one thing some of our contributions have in common with many others is the lack of testing. I want to change that. I''d like to help lead an effort to make the facebooker tests better. One thing that I think would help is a little better

In my app, I store the job key when a worker is fired off and then check back in periodically to see how its doing. The workers delete themselves when they''re done. I would expect when I try to get a worker that has been deleted, I would get nil or a proper exception, but instead I get: >> MiddleMan.worker(''foobar'') NoMethodError: undefined method

I'm working on an application that is backed by Postfix 2.3.8 and Dovecot 1.0.13, configured with virtual domains, for handling messaging. I need to be able to send the notification (such as "You've received a new message on SomeAwesomeService. Click here to check it out", It's evil, I know) to a different email address, such as a mobile device. Eventually, we want

I'm getting strange timeouts occasionally on Dovecot 1.0.rc15 on Debian 4.0, and haven't been able to figure out the cause. $ ./src/imaptest user=test%d at imaptest.com host=localhost pass=foo mbox=~/dovecot-crlf - select=0 Logi Logo 100% 100% 2 4 7/ 10 0 0 10/ 10 0 0 10/ 10 0 0 10/ 10 0 0 10/ 10 0 0 10/ 10 0 0 10/ 10 0 0