On Mar 30, 2009, at 3/304:47 PM , xfile80303 wrote:
Is there a way to utilize this to only rewrite page render requests
and
not component or asset requests? I know it is pretty early on in the
request lifespan, but without this discrimination this feature is not
nearly as useful to me (and possibly others?).
It's really very early in the request handling pipeline. Maybe
Tapestry
should add some way (maybe methods in the Request instance) that
tells if
the given request is an page one or an event one or an asset one or
etc.
-1. Although there are times when I've thought this might be handy,
the determination of the request type is resolved via the
MasterDispatcher service; if you really need to know the request type,
then the operation you're performing probably needs to come later in
the flow of operations.
Robert
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
