Re: Documenting all HTTP requests to an application

2011-05-12 Thread Alec Munro
Nope, haven't needed it yet. This case is a bit special because I want unique routes, but I want to filter out query string values (and ids in urls). I think you have my original question more or less correct. I want to know how the app is being used, so when I rewrite it using Pyramid, I can make

Re: Documenting all HTTP requests to an application

2011-05-11 Thread Alec Munro
nning 'sort -u' across the resultant file will > give you all of the unique addresses visited by users during the > logging period. > >         — Alice. > > On 2011-05-10 11:59:16 -0700, Alec Munro said: > > > > > > > > > D'oh! > >

Re: Documenting all HTTP requests to an application

2011-05-10 Thread Alec Munro
D'oh! I should have specified that I'm using Pylons 0.96 for this particular application. Thanks, Alec On May 10, 3:51 pm, Jasper van den Bosch wrote: > If you use traversal, perhaps in the constructor of your Root resource? > > On 10 May 2011 20:40, Alec Munro wrote: &

Documenting all HTTP requests to an application

2011-05-10 Thread Alec Munro
Hi list, I want to create a map of all the requests to an application, to make it easier to refactor it without breaking it's interfaces. What's the easiest place to add a function to be called for every request? Thanks, Alec -- You received this message because you are subscribed to the Google