doh.. process_view is what I am after..sorry for the noise
On 20/05/2006, at 11:37 AM, Ian Holsman wrote:
>
> I'm just thinking out loud here, but I was wondering what the others
> developers thought of having a event/hook
> which would capture the URL request just after it has been resolved.
> (and possibly just after it is executed)
>
> so the input of the function would be something like
>
> request, view_function_name_about_to_called , { parameters being
> passed to it}
>
> it's very similar to middleware, but it includes the view we are
> calling.
>
> why?
>
> well.. I'd like to get some stats about my application's usage and
> thought it would be easier (and more accurate) to do it in the
> request processing phase instead of parsing a log file, or inserting
> a web-bug/clear-gif at the end of the HTML page.
>
> regards
> Ian
>
> >
X-Google-Language: ENGLISH,ASCII-7-bit
Received: by 10.54.63.18 with SMTP id l18mr123382wra;
Fri, 19 May 2006 18:59:24 -0700 (PDT)
Return-Path: <[EMAIL PROTECTED]>
Received: from circe.holsman.net (218-214-209-234.people.net.au
[218.214.209.234])
by mx.googlegroups.com with ESMTP id v23si173480cwb.2006.05.19.18.59.13;
Fri, 19 May 2006 18:59:24 -0700 (PDT)
Received-SPF: neutral (googlegroups.com: 218.214.209.234 is neither permitted
nor denied by domain of [EMAIL PROTECTED])
Received: from [127.0.0.1] (localhost [127.0.0.1])
by circe.holsman.net (Postfix) with ESMTP id 52DE21C42AF
for <[email protected]>; Sat, 20 May 2006 11:58:53
+1000 (EST)
Mime-Version: 1.0
Content-Type: text/plain
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-Id: <[EMAIL PROTECTED]>
From: Ian Holsman <[EMAIL PROTECTED]>
Subject: Re: logging
Date: Sat, 20 May 2006 11:58:52 +1000
To: [email protected]
X-Mailer: Apple Mail (2.750)
doh.. process_view is what I am after..sorry for the noise
On 20/05/2006, at 11:37 AM, Ian Holsman wrote:
>
> I'm just thinking out loud here, but I was wondering what the others
> developers thought of having a event/hook
> which would capture the URL request just after it has been resolved.
> (and possibly just after it is executed)
>
> so the input of the function would be something like
>
> request, view_function_name_about_to_called , { parameters being
> passed to it}
>
> it's very similar to middleware, but it includes the view we are
> calling.
>
> why?
>
> well.. I'd like to get some stats about my application's usage and
> thought it would be easier (and more accurate) to do it in the
> request processing phase instead of parsing a log file, or inserting
> a web-bug/clear-gif at the end of the HTML page.
>
> regards
> Ian
>
> >
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers
-~----------~----~----~----~------~----~------~--~---
