Re: [web2py] Re: bug in app-specific routing

2010-09-01 Thread Jonathan Lundell
On Sep 1, 2010, at 7:32 AM, mdipierro wrote: > > request.application is already there. Where is it used and the > appmname is not available? If request were always available, we could store the appropriate params link there as request.params. Here's an example (not, I think, the only one): str

[web2py] Re: bug in app-specific routing

2010-09-01 Thread mdipierro
request.application is already there. Where is it used and the appmname is not available? On Sep 1, 9:17 am, Jonathan Lundell wrote: > On Sep 1, 2010, at 7:01 AM, mdipierro wrote: > > > > > No we cannot. > > > rewrite.params[appname]? > > That structure exists, but where would appname come from

Re: [web2py] Re: bug in app-specific routing

2010-09-01 Thread Jonathan Lundell
On Sep 1, 2010, at 7:01 AM, mdipierro wrote: > > No we cannot. > > rewrite.params[appname]? That structure exists, but where would appname come from (in general)? I think that's the same problem. We could maybe stick it in request or response, but params is used a couple of places where that'

[web2py] Re: bug in app-specific routing

2010-09-01 Thread mdipierro
No we cannot. rewrite.params[appname]? On Sep 1, 8:46 am, Jonathan Lundell wrote: > Massimo, it dawned on me (literally--I was lying in bed with the sun coming > up) that we can't use the global rewrite.params to store the app-specific > routing parameters because it's not thread-safe. Right?