From: Marek Potociar <marek.potociar_at_oracle.com>
Date: Mon, 27 Jun 2011 14:22:45 +0200

The assumption was that we need to be able to control the features up to the invocation level. Here's a potential use case:

// All communication on this client is audited by default
client.register(AuditingFilter.class);

// adding a specific resource security filter for the link
Link resource = client.link("http://some.resource/uri/").register(SomeResourceSecureHandler.class);

This seems to be a common use case and we should support it.

Marek

On 06/27/2011 02:00 PM, Sergey Beryozkin wrote:
> I'd prefer per-client Feature registration or per-runtime (affecting all the clients) one