[ http://issues.apache.org/jira/browse/JCR-235?page=comments#action_12331150 ]
Tobias Strasser commented on JCR-235: ------------------------------------- suggest to extends the NamespaceResolver interface by the respective QName translation methods. This would enable a broader usage of an eventual cache. fruthermore could the session local namespace/qname resolvers be sensitive to local namespace mappings. > Cache jcr name to QName mappings > -------------------------------- > > Key: JCR-235 > URL: http://issues.apache.org/jira/browse/JCR-235 > Project: Jackrabbit > Type: Improvement > Components: core > Reporter: Marcel Reutegger > Assignee: Stefan Guggisberg > Priority: Minor > Attachments: QNameResolver.patch > > Currently jcr names are always parsed and resolved into QName instances. > Introducing a cache would increase performance and also save memory because > well known and often used jcr names would always return the same QName > instance from cache. > Testing with common read operations shows a performance improvement of about > 25%. > The test involved the following methods on Node interface: > - getProperty() > - getProperties() > - getName() > - getPath() > - isLocked() > - isNodeType() > - getPrimaryNodeType() > - hasNodes() > - getNodes() > Attached proposed implementation of a QNameResolver. > Please comment. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
