Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.4.0
-
Fix Version/s: 6.6.0
-
Component/s: wicket-atmosphere
-
Labels:None
Description
With a function on AtmosphereResource, rather than a predicate, it is possible to filter on attributes in the AtmosphereRequest. This would allow you to create filters that differentiate on the receiver, without relying on the heavy-weight contextAwareFilter().
Activity
Functions was not going to work, because the payload and resource were needed, so I created a tuple containing both. You how have access to the the payload and the resource. BTW, wicket-atmosphere has always had a dependency on guava, not just for Predicate, but also for other classes.
Show
Emond Papegaaij
added a comment - Functions was not going to work, because the payload and resource were needed, so I created a tuple containing both. You how have access to the the payload and the resource. BTW, wicket-atmosphere has always had a dependency on guava, not just for Predicate, but also for other classes.
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 6.6.0 [ 12323963 ] | |
| Resolution | Fixed [ 1 ] |
I'll vote for this! The predicate also creates a dependecy on google jsut for the sake of using one single interface. A Wicket specific one would be mor appropiate and handling over the AtmosphereResource also would help for corner cases.