Re: HTMLPurifier and the "Input" class

On Sun, Apr 7, 2013 at 1:04 AM, Shad Laws <shad-xpYdmXCiSuZWk0Htik3J/[email protected]> wrote:

> Hey Bharat,
>
> A thought on Gallery::ready() - it seems like it'd be a lot more
> straightforward if it had access to the request.  In addition to the
> reasons you give below, it also calls Request::user_agent().
>
> Two other possibilities:
> - build the request, call Gallery::ready(), then execute the request
> - make Gallery_Controller() that overrides Kohana_Controller() and
> adds a before() function that calls Gallery::ready()
>
>
I originally tried to do this by calling Request::factory() twice - once in
bootstrap and once in index.  That didn't work - I can't remember the exact
details but it was challenging to debug.  However, I think it's reasonable
to move gallery::ready into index.php so the code would be:

$request = Request::factory(...);
Gallery::ready();
$request->execute(...);

Kohana 2's "system.post_routing" concept is difficult to access because
that happens inside of execute() - but I think it's fair to say that
"system.ready" can happen right before we call execute().

Want to try that and see if it works?

------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire 
the most talented Cisco Certified professionals. Visit the 
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html

__[ g a l l e r y - d e v e l ]_________________________

[ list info/archive --> http://gallery.sf.net/lists.php ]
[ gallery info/FAQ/download --> http://gallery.sf.net ]