Create a small bit of middleware to log the environ['REQUEST_URI'] (or
other value, as appropriate) of each GET. You can then direct that
logger to output to a file, another handler (i.e. you could write one
which logs to your database of choice and de-duplicates), etc.
Logging to a file then running '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!
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
<jap...@gmail.com> wrote:
If you use traversal, perhaps in the constructor of your Root resource?
On 10 May 2011 20:40, Alec Munro
<alecmu...@gmail.com> wrote:
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 Groups
"pylons-devel" group.
To post to this group, send email to
pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
--
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com.
To unsubscribe from this group, send email to
pylons-devel+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/pylons-devel?hl=en.
