search for: ted_spam

I''m either missing a step, confused or seeing some odd behavior with ActiveRecord''s serialize feature. When I load an ActiveRecord object from the database, my serialized attribute is a YAML::Object, not the original object. My code is based on an example of this capability in the "Agile Web Dev. w/ Rails" book (p. 196). In create.sql: <code> create table

Hey everyone, I''m still getting up to speed with Rails and Ruby. Is there a best practice technique for kicking off a thread to work on an activity in the background? Here''s the scenario: the user performs an action that triggers e-mails to be sent. (I''m using ActionMailer). My app acknowledges with a message to the user that the messages have been sent. I would

I''m trying to debug a bug in my code and am looking for some general advice on how to go about isolating the problem. The problem: My Rails application talks to a WebDAV server via HTTPS. Thanks to the Ruby standard library, I was able to make authentication over SSL happen with just a few lines of code. Awesome! Now it gets a bit obscure. I''m using a PROPFIND request to the

Hello! My setup is Rails 1.1 with Apache 2.x proxying the Rails stuff to lighttpd. I know how to set up Apache to secure my entire Rails app to require a username/password challenge. Is it possible to set up the challenge for only parts of my application? E.g., let''s say I have a "pub" controller whose views are accessible to anyone. I am already implementing user