 | Start a set with this search |
 | Include this search in one of my sets |
 | Exclude this search from one of my sets |
 | Permalink to these results Paste this link in email or IM: |
 | Atom feed for tracking future search results Paste this URL into your reader: |
9 messages in org.apache.jakarta.slide-devRe: proposal to move JCR RI to incubator| From | Sent On | Attachments |
|---|---|---|
| Roy T. Fielding | Aug 3, 2004 5:29 pm | |
| Gianugo Rabellino | Aug 4, 2004 1:14 am | |
| Daniel Florey | Aug 4, 2004 1:51 am | |
| Daniel Florey | Aug 4, 2004 1:58 am | |
| Mats Norén | Aug 4, 2004 4:22 am | |
| Stefan Guggisberg | Aug 4, 2004 6:13 am | |
| David Nuescheler | Aug 5, 2004 3:01 am | |
| Paul Russell | Aug 5, 2004 4:06 am | |
| Andrew Savory | Aug 6, 2004 3:42 am |
| Permalink for this message Paste this link in email or IM: |
| Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: proposal to move JCR RI to incubator | Actions... |
|---|---|---|
| From: | David Nuescheler (davi...@yahoo.com) | |
| Date: | Aug 5, 2004 3:01:25 am | |
| List: | org.apache.jakarta.slide-dev | |
Hi Gianugo,
I will try to answer your second question:
2. project scope. We all know that Tomcat is a RI as well, but its success has gone far beyond that. I would welcome jcrri as an Apache effort if the project scope is making a worthwile, performant and stable ASF-licensed implementation out of it, something that can be used in production: if, on the contrary, this impl is meant just as a barebone spec ri, it's still a very nice thing to have, but it could probably keep on living on slide as a more or less visible subproject.
It is our intention to build a complete content repository with all the features and functionalities that are necessary use the repository in real-life, not just a theoretical RI. It is certainly our intention to create a full-fledge repository which will hard to beat from a functional perspective, which means that we will not just make sure that the RI will pass the repository, but that it fullfill the spec to its full extent, and beyond.
As you might have seen we already put features into the reference implementation that cannot be specified in the jsr-170 spec but are necessary to operate a content repository in real life (like a nodetype definition api).
In my mind the Apache JCR Project (wherever it should end up) should be the first place to turn to, for any application developer that wants to start development with a Content Repository.
As a consequence, then, my first proposal would be rethink the name: jcr or jcrri aren't "product" names, and they smell bad of "just" RI (a quick "grep '.*j.*c.*r.*' /usr/share/dict/words" didn't blow my mind, the best alternative being "rejoicer".
.. or JuiCeR ;)) ?
Count me in, I'd be glad to help out in my Copious Free Time (urgh).
Thanks.
regards, David
__________________________________ Do you Yahoo!? Yahoo! Mail - 50x more storage than other providers! http://promotions.yahoo.com/new_mail