jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Julian Reschke <julian.resc...@gmx.de>
Subject Re: Observation design (Was: svn commit: r1351414 - in /jackrabbit/oak/trunk/oak-core/src/main/java/org/apache/jackrabbit/oak: api/ChangeSet.java api/ContentSession.java core/ContentSessionImpl.java)
Date Wed, 20 Jun 2012 15:03:20 GMT
On 2012-06-20 16:44, Jukka Zitting wrote:
> Hi,
> On Wed, Jun 20, 2012 at 3:40 PM, Michael Dürig <mduerig@apache.org> wrote:
>> Leaving userdata out works for me. Not sure what the "spec police" will say
>> though ;-)
> To pass the TCK without user data we'll need to set the observation
> supported descriptor to false. I'm OK with that as long as we still
> implement most of the JCR observation interfaces and document the less
> strict observation contract that we are supporting.
> If needed, we could propose to JSR 333 to relax the specified
> observation contract or at to introduce more fine-grained descriptors
> that allow an implementation like ours to declare at least some
> observation functionality as supported.

"The optimal number of optional features in an API/protocol is zero".

Would it be possible to summarize what makes it hard to support userdata?

> ...

Best regards, Julian

View raw message