sszuev commented on issue #1961: URL: https://github.com/apache/jena/issues/1961#issuecomment-1660415389
I understand your example. Of course, thread-safe Graphs cannot replace transactional ones. I think they have different fields of application. Analogy: `Redis` vs `ConcurrentHashMap`. It seems to me that the main question in this issue is whether it will be useful to anyone or not. If not, then perhaps we shouldn't add this functionality to Apache Jena. That's why I'm asking here: we need more examples of possible use. I also asked in the OWLCS group. There is definitely one example of use: ONTAPI. I'm thinking of other examples, but so far such examples are purely speculative. For example, we could collect a graph from various sources simultaneously and display it as a tree or a set of axioms on various devices. Perhaps even co-edit (but it seems a transactional graph is more suitable when edit). Maybe we could use a thread-safe graph as kind of cache. The `Caffeine` cache uses `ConcurrentHashMap`, so why not. And of course, a thread-safe graph-wrapper has some advantages over a transactional one - performance and the ability to wrap any graph. Maybe it would be useful for someone. I asked a colleague about additional examples, if we come up with something, I will edit this comment. -- 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]
