Re: Conflicting invocation constraints

On Feb 14, 2007, at 6:00 AM, Mark Brouwer wrote:

> I'm trying to understand what happens when invocation constraints
> set by
> the client conflict with server side imposed constraints. From the
> code
> I've seen it appears both set of constraints are combined by the
> invocation handler before making an invocation, but combining as
> specified by InvocationConstraints.combine() doesn't detect these
> conflicts.
>
> I was not able to find 'client' side code that detects these conflicts
> but that is likely due to getting lost during my search and not
> comprehending what I've seen. Where can I find how constraint
> conflict detection is supposed to work as part of the endpoints or
> higher layers in the Jini ERI stack.

Whether constraints conflict with each other is a question that needs
to be answered by the Endpoint implementation, not by the generic
constraints mechanism.

In the SSL endpoint code, this process happens in the SslEndpointImpl
class, starting with the getCallContext method.  Note that the basic
approach is to compute SSL configurations that match the specified
constraints; if none match, then the constraints must be
unsatisfiable, which includes the case of them conflicting with each
other.

As a side note, in pre-release versions of the code, constraints did
have a notion of conflicting constraints, but this turned out to be
both quite complicated and not really right.

- Tim

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]