[If you're replying point by point, please try to quote the lines you are responding to. It will make the discussion easier to follow.]
Cris Shupp wrote: > Marnen, > > You are fast... > > Class variables... got it! ;-) :) [...] > I really do not want to use a yaml file. Some of the config data will > include passwords to other systems that the worker threads will need to > perform their duties. Also, the admins will get cranky if I make them > modify a yaml file. > > If I use a 'singleton' active record I do need to figure out how to > encrypt the password in the database. Perhaps. But you don't need to take this approach. > > If I use a static, err class variable, I am more than willing to roll > the dice and assume no one will dump mongrel's memory and hunt for it. > > I am very willing to use the class variable approach, This is the wrong approach. If I understand the problem correctly, your first approach (using instance variables) is almost correct -- just get rid of the initialize method as I explained above. > but I am highly > curious how to build a 'singleton' model to make use of the various > active record goodies (assuming I can delete it upon startup). I really doubt that this is worth doing. > > > Thanks, > > Cris Best, -- Marnen Laibow-Koser http://www.marnen.org [email protected] -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
