But Sijo needs is justified when tracing "who" is doing something to your model.
Sijo, look into this screencast from Ryan Bates (http://railscasts.com/ episodes/119-session-based-model). It provides with good leads for a solution on what your looking. In short what you want to provide your model with is an execution context which will contain the user id (not the whole session). What you have to keep in mind is to avoid putting anything at the class level since it would prevent your code from bring Threadsafe (which Rails 2.2 is supposed to be). Jean-Marc Lagacé http://m2i3.com/blog/jean-marc --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
