> Is there any way around this situation? Is there some way to keep the
> instantiated class alive so it can be used in subsequent actions?
Sure, for the non user-specific parts, you can lazy-load and cache:
class Expensive
def self.share_me
@some_val ||= expensive_calculation
end
end
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
