On Wed, Mar 17, 2010 at 6:42 PM, Thomas Müller wrote:
> I'm wondering what is the *most* problematic features to verify the
> architecture:
> - security
> - orderable child nodes
> - same name siblings
> - locking
> - transactions
> - clustering
> - observation
> - workspaces
> - node types
> - la
Hi Thomas,
results look good! I think it's clear that this is not a final and
fair comparison, but it's good to be able to see which of the missing
features actually makes it more complex and/or slower while they will
be implemented.
On Wed, Mar 17, 2010 at 19:42, Thomas Müller wrote:
> I'm wond
Hi,
> i doubt that the results of this comparison is any way significant.
It was not supposed to be a fair comparison :-) Of course the
prototype doesn't implement all features. For example path are parsed
in a very simplistic way. I don't think the end result will be as fast
as the prototype. St
On Wed, Mar 17, 2010 at 4:45 PM, Stefan Guggisberg
wrote:
> jackrabbit is the reference implementation of JCR 1.0/2.0 and therefore has
> to fully support all the spec'ed features (node types, same name siblings,
> locking, access control, etc etc).
I agree that the default distribution should com
On Tue, Mar 16, 2010 at 7:46 PM, Thomas Müller wrote:
> Hi,
>
> I have some early performance test results: There is a test with 3
> levels of child nodes (each node 20 children)
> (TestSimple.createReadNodes).
>
> With the JDBC storage and the H2 database, this is about 14 times
> faster than the
On Wed, Mar 17, 2010 at 9:34 AM, Thomas Müller wrote:
>> In your opinion, which part make the most of performance contribution?
> It's hard to say. I would rather spend my time to work on the
> prototype than to find out. To keep the prototype fast, it's important
Understand it will take effort to
Hi,
I am currently adding support for more JSR-283 API
(AccessControlManager) to RMI. I would also like to add support for the
Jackrabbit API extensions PrincipalManager and UserManager.
How is this intended to be done ?
Do we create another ClientAdapterFactory or do we extend the existing
adap
Hi,
On 17.03.2010 12:19, Thomas Müller wrote:
> Hi,
>
>> premature optimization
>
> Sure, premature optimization should be avoided. But sometimes you need
> to validate that a certain architecture / algorithm doesn't result in
> very slow or unmaintainable code. I mean, that's the reason to writ
[
https://issues.apache.org/jira/browse/JCR-2575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-2575.
---
Resolution: Fixed
Fix Version/s: 2.1.0
Added test case and fix in revision: 924238
> In
Incorrect excerpt for index aggregates
--
Key: JCR-2575
URL: https://issues.apache.org/jira/browse/JCR-2575
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-core
Hi,
> premature optimization
Sure, premature optimization should be avoided. But sometimes you need
to validate that a certain architecture / algorithm doesn't result in
very slow or unmaintainable code. I mean, that's the reason to write a
prototype: so you can actually test it.
> clean and eas
[
https://issues.apache.org/jira/browse/JCR-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved JCR-2574.
---
Resolution: Fixed
Fix Version/s: 2.1.0
Added test case and fix in revision: 924224
> Ro
Hi
Given as such, this looks promising, event though the prototype
currently probably misses tasks that Jackrabbit currently does, right ?
I am thinking of data validation against the node types when storing.
Regards
Felix
On 16.03.2010 19:46, Thomas Müller wrote:
> Hi,
>
> I have some early pe
Hi,
On 17.03.2010 10:34, Thomas Müller wrote:
> Hi,
>
>> In your opinion, which part make the most of performance contribution?
>
> It's hard to say. I would rather spend my time to work on the
> prototype than to find out.
Agreed. And at the end of the day, it is probably not very interesting
Row.getValue("rep:excerpt(.)") may throw ArrayIndexOutOfBoundsException
---
Key: JCR-2574
URL: https://issues.apache.org/jira/browse/JCR-2574
Project: Jackrabbit Content Repository
Hi,
> In your opinion, which part make the most of performance contribution?
It's hard to say. I would rather spend my time to work on the
prototype than to find out. To keep the prototype fast, it's important
to always check performance. I guess we didn't always do that for
Jackrabbit unfortunat
[
https://issues.apache.org/jira/browse/JCR-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2572:
Component/s: (was: versioning)
(was: JCR API)
jackrabbit-spi2dav
adjusting
[
https://issues.apache.org/jira/browse/JCR-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela resolved JCR-2572.
-
Resolution: Duplicate
duplicate of JCR-2472
> session.move() fails with mix:versionable nodes
> --
[
https://issues.apache.org/jira/browse/JCR-2573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated JCR-2573:
Fix Version/s: 2.2.0
> Performance of AC Evaluation
>
>
> Key: JCR-2573
Performance of AC Evaluation
Key: JCR-2573
URL: https://issues.apache.org/jira/browse/JCR-2573
Project: Jackrabbit Content Repository
Issue Type: Improvement
Components: jackrabbit-core
Affects Vers
20 matches
Mail list logo
