How about just passing in the session data hash when you call the
particular workling ob method, something like:
### in ./app/workers/foo_worker.rb
class FooWorker < Workling::Base
def bar(options)
session_data = options[:session_data])
# do something with session.data hash ...
end
end
### in some_meth in ./app/controllers/some_controller.rb
...
FooWorker.asynch_bar(:session_data=>session.data)
...
Jeff
On May 24, 4:06 pm, PierreW <[email protected]> wrote:
> Hi guys,
>
> I have been trying to access session data (I am using the
> ActiveRecordStore option) from a background process (Workling in my
> case - but I suspect it should be the same for others). It seems to me
> it should be fairly obvious since I can pass the session_id to the
> background and the session data is in the DB anyway. But I can't make
> it to work.
>
> I looked around and saw a note on this group from Fred:
> "you'll need to instantiate the appropriate subclass of
> ActionController::SessionStore" but I don't understand this.
>
> Could someone point me in the right direction?
>
> Thanks!
> Pierre
>
> --
> 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
> athttp://groups.google.com/group/rubyonrails-talk?hl=en.
--
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.
