Josh West wrote:
>> First off, don't attempt to start a new thread by replying to a previous
>> one. Many newsreaders will merge the two, confusing the hell out of
>> everyone and generally not helping.
>>
>
> Ahh, yes. I see what you mean. Explains why it didn't appear the first
> time I po
>
> First off, don't attempt to start a new thread by replying to a previous
> one. Many newsreaders will merge the two, confusing the hell out of
> everyone and generally not helping.
>
Ahh, yes. I see what you mean. Explains why it didn't appear the first
time I posted (until later..).
So
Josh West wrote:
> Kind and wise fellows,
> [...]
Please see my separate reply with the same subject line but in a new
thread. That reply explains *why* it's in a new thread.
regards
Steve
--
Steve Holden+1 571 484 6266 +1 800 494 3119
Holden Web LLC/Ltd http://www.holdenwe
> Kind and wise fellows,
>
> I've got a web application with the following structure:
>
> 1) module of 100 functions corresponding to user actions (e.g.
> "update_profile()", "organisations_list()")
> 2) a wsgi callable which maps urls to functions eg
> /organisations/list/?sort=date_created is
Kind and wise fellows,
I've got a web application with the following structure:
1) module of 100 functions corresponding to user actions (e.g.
"update_profile()", "organisations_list()")
2) a wsgi callable which maps urls to functions eg
/organisations/list/?sort=date_created is mapped to
orga
Hello
I've got a web application with the following structure:
1) module of 100 functions corresponding to user actions (e.g.
"update_profile()", "organisations_list()")
2) a wsgi callable which maps urls to functions eg
/organisations/list/?sort=date_created is mapped to
organisations_list("date
