[
https://issues.apache.org/jira/browse/JENA-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13418976#comment-13418976
]
Piotr Hołubowicz commented on JENA-281:
---
Thanks for the clarification. I was referring
[
https://issues.apache.org/jira/browse/JENA-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419017#comment-13419017
]
Andy Seaborne commented on JENA-281:
You are more than welcome to submit a patch for
[
https://issues.apache.org/jira/browse/JENA-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419022#comment-13419022
]
Piotr Hołubowicz commented on JENA-281:
---
Makes sense, thanks. Should I need to modify
[
https://issues.apache.org/jira/browse/JENA-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419024#comment-13419024
]
Andy Seaborne commented on JENA-256:
You can have separate non-nested transactions by
[
https://issues.apache.org/jira/browse/JENA-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13419026#comment-13419026
]
Andy Seaborne commented on JENA-279:
If we keep the cache, the use of soft references
In JENA-279, the issue of whether the NodeCache serves any useful
purpose these days has come up.
Proposal: Remove the node cache
Proposal: Remove the triple cache
Node cache:
There are two reasons for the cache: time saving (object creation costs)
and space saving (reuse nodes). I'm not
[
https://issues.apache.org/jira/browse/JENA-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andy Seaborne updated JENA-284:
---
Issue Type: Improvement (was: Bug)
Summary: Support for cygwin in apache-jena scripts. (was:
Here are some thoughts on Jena3-timeframe changes - we have the
opportunity to make changes and while we can't change too much without
going into a black hole, a few key changes can be done.
== Node Hierarchy
At the moment, every node has an Object label in Node itself and it
keys the cache,
+1 on removal of both the node and triple caches.
In addition to the reasons already discussed, there is also the fact
that Node.create() uses a global lock, which is going to be really bad
for concurrency!
Triple.create() doesn't do any locking, which appears to work out OK
in this specific
Additionally, a fun thing to look at for Node would be to have a
static cache pre-populated with commonly used resources (RDF, RDFS,
OWL, etc.), similar to Java's Integer.valueOf(int) method. That could
be useful.
-Stephen
On Fri, Jul 20, 2012 at 8:31 AM, Stephen Allen sal...@apache.org wrote:
10 matches
Mail list logo