>> But it is do-able, although not easy, I don't think you can get away
>> with just trying to access the session array itself in a thread that's
>> out of the request loop.
Sorry, this is a topic of interest to me that noone else is ever
interested in talking about.
PPS: REALLY, if you de
Jonathan Rochkind wrote:
>
> But it is do-able, although not easy, I don't think you can get away
> with just trying to access the session array itself in a thread that's
> out of the request loop.
I'd add it's do-able ONLY if you are using a server-side session store.
NOT if you are using th
Sudhi Kulkarni wrote:
> Then in one of the periodic update methods if I access the
> session[:executing] it is not updated to "done". Is there a problem if I
> try to update session variable in a different thread?
Actually, this is precisely what I was trying to do in another thread
here where
On May 27, 4:36 am, Sudhi Kulkarni
wrote:
> Frederick Cheung wrote:
> How do I know whether rails has closed out and pushed the cookie back to
> client?
There's going to be a pretty narrow window after your action method
returns and before rails has got as far as session cleanup. I can't
thin
Frederick Cheung wrote:
> On May 26, 10:20�am, Sudhi Kulkarni
> wrote:
>> session[:executing] it is not updated to "done". Is there a problem if I
>> try to update session variable in a different thread?
>>
>
> If this ends up setting the session after rails has closed out the
> session (ie push
On May 26, 10:20 am, Sudhi Kulkarni
wrote:
> Hi,
>
> I have a controller code which does the following
>
> t1= Thread.new {
> #some code
> session[:executing] = "done"
> }
>
> Then in one of the periodic update methods if I access the
> session[:executing] it is not updated to
6 matches
Mail list logo
