[ https://issues.apache.org/jira/browse/TAP5-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667735#action_12667735
]
Howard M. Lewis Ship commented on TAP5-476:
-------------------------------------------
To me "is logged on" is an application-specific concept that I don't want to hard code. Further,
it quickly grows from two states (anonymous or logged-in) to multiple states (what roles or
privileges does the user have).
> Have a common handler/filter pipeline for both component event and page render requests,
to make it easier to add filters that apply to both types of requests
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-476
> URL: https://issues.apache.org/jira/browse/TAP5-476
> Project: Tapestry 5
> Issue Type: New Feature
> Components: tapestry-core
> Affects Versions: 5.1.0.0
> Reporter: Howard M. Lewis Ship
>
> Currently, if you want to put a filter in place that afects both types of request, you
have to a contribute a ComponentEventRequestFilter to the ComponentEventRequestHandler service,
and a nearly identical PageRenderRequestFilter to the PageRenderRequestHandler service.
> It would be nice if there was a service that acted as a facade around the two existing
pipelines. The terminator of that pipeline could forward the request into one of the two
existing pipelines.
> The common example of this is a "is logged in" filter that sends a redirect if the user
is not logged in; you want to do this for both types of requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|