Re: Ajax request, ERXRedirect and ERXThreadStorage
Re: Ajax request, ERXRedirect and ERXThreadStorage
- Subject: Re: Ajax request, ERXRedirect and ERXThreadStorage
- From: Paul Hoadley <email@hidden>
- Date: Wed, 13 Jul 2016 09:36:45 +0930
On 13 Jul 2016, at 1:41 AM, Chuck Hill <email@hidden> wrote:
As long as you have more than one worker thread, there is no guarantee which will process which request.
I logged out the thread names, and that didn’t seem to be the problem. The same worker thread was involved from the Ajax action through to sending out the re-direct. Do you have a session you can stash it in?
Yeah, that’s my workaround. It’s awkward, though, because the single R-R lifespan of ERXThreadStorage is just perfect for this use case. In fact, I end up moving the informational messages into ERXThreadStorage at some point just to ensure they disappear at the right time (because they shouldn’t persist into the next R-R, they’re just for one-off display). I couldn’t seem to simulate it just using the session.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden