RE: [Bug 3] Bindings draft should specify if all properties MUST have same value on all bindings

It seems to me that a live property inherently has the quality that its
output can depend on an arbitrary computational process, which can make use
of any aspect of the server's state it has access to. This includes
bindings.

While it is reasonable for servers to make use of this capability sparingly,
it's also reasonable for them to have live properties that depend on binding
state if it supports a particular application.

Julian writes:
> Also, the statement as proposed, sort of
> *encourages* implementers to have live properties 
> varying by binding.  IMHO, they shouldn't (as 
> properties are part of the state of the resource 
> or computed based on the state of a resource), and 
> thus should not vary at all.

There's nothing in 2518 that implies a live property's computation depends
only on the state of the resource. It would be prefectly valid to have a
live property that returned a random number.

I'm not too worried about encouraging binding-specific properties, as I
believe implementors would be able to see the potential usability drawbacks
of such properties.

- Jim

Received on Thursday, 9 December 2004 00:13:21 UTC