sszuev commented on issue #1961: URL: https://github.com/apache/jena/issues/1961#issuecomment-1641813466
Well, the code is open for both [ONT-API](https://github.com/owlcs/ont-api) and [concurrent-rdf-graph](https://github.com/sszuev/concurrent-rdf-graph). ONT-API is an implementation of [OWL-API](https://github.com/owlcs/owlapi) api, we can't use transactions, there are RW-lock mechanism. We have to follow OWL-API rules. It supports concurrent access to OWL via `java.util.concurrent.locks.ReadWriteLock`. Also, I don't quite understand how transactions could help if we have Streams and don't want to put everything in memory. Usually transactions are used in the top-level, maybe with help of AOP. In ONTAPI we have neither top-level nor AOP. [ReadWriteLockingGraph](https://github.com/sszuev/concurrent-rdf-graph/blob/main/src/main/kotlin/ReadWriteLockingGraph.kt) offers such way. If we have a lot of read-operations, and few write ones, no so much memory is required. In concurrent-rdf-graph there are tests. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
