Not spawn new processes based on 'request.path'?

[TJ]

I'm having a problem where Passenger is spawning several processes
when a user gets to submit my registration process, and so a lot of
users are getting duplicate records because of that.

Is that a way that I can choose not to spawn new processes based on
"request.path" the user might be on? For instance, not spawn any new
processes if the user is on "/registration/new" or "/registration/
create" for example.

Thanks a lot.

TJ

[TJ]

I can't believe that no one knows (not even the authors) how to access
the path of the current page through Phusion... Is that really
impossible?

Thanks.

[Stephen]

Honestly, it doesn't sound like a passenger problem as much as
something to do with your app.

Passenger is spawns threads as needed and isn't something your app
should have to care about to function correctly.

Perhaps you could explain your setup a little more? maybe your doing
some sort of caching/memoization thats not coherent between all the
threads? just a guess without more info.

[Hongli Lai]

On Fri, Dec 11, 2009 at 4:07 PM, TJ <sk8t...@yahoo.com> wrote:
> I can't believe that no one knows (not even the authors) how to access
> the path of the current page through Phusion... Is that really
> impossible?

It is not possible right now. But such an option would only be a
workaround for the real problem. Shouldn't your application check for
duplicates before committing the registration?

--
Phusion | The Computer Science Company

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)