[
https://issues.apache.org/jira/browse/JCR-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154230#comment-13154230
]
Julian Reschke commented on JCR-2541:
-------------------------------------
I discussed this with Marcel last week, summary:
- implement the EventJournal as a "feed" resource
- filtering happens client-side, same as for observation
- feed format would be Atom (RFC 4287) unless there's a strong reason not to
- getting events "since" can be implemented using the If-None-Match/Vary, using
the timestamp as etag
To be discussed: discovery of the feed URI
> spi2dav : EventJournal not implemented
> ---------------------------------------
>
> Key: JCR-2541
> URL: https://issues.apache.org/jira/browse/JCR-2541
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-jcr-server, jackrabbit-spi2dav, JCR 2.0,
> observation
> Affects Versions: 2.0
> Reporter: angela
>
> i didn't look at the details just realized that all EventJournalTest of the
> TCK fail in the setup
> jcr2spi - spi2dav(ex) - jcr-server.
> i assume that this is due to missing implementation (the corresponding SPI
> method throws UnsupportedRepositoryOperationException).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
