improve WebRequestServicerFilter and provide the service information
--------------------------------------------------------------------
Key: TAPESTRY-982
URL: http://issues.apache.org/jira/browse/TAPESTRY-982
Project: Tapestry
Type: Improvement
Versions: 4.1
Reporter: Henri Dupre
Priority: Minor
Currently, in the request processing pipeline, Tapestry extracts the service
information from the request in the requestCycleFactory method. This makes it
cumbersome to write effective WebRequestServicerFilter and filter according to
the service e.g. create a hibernate session for a page/externalpage/... service
but not for an asset. Same for serializing requests: serialize
page/external/... request but allow concurrent execution of an asset service.
Could the service information be extracted earlier and be moved to the
WebRequest object?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
