Greetings, Given that the Cassandra server can host multiple client and those clients can open the same graph on the server simultaneously. Basically two updatable synchronized views on one data set.
Assume graph A is opened on client X and client Y and applications at X and Y both register listeners on the graph. If application at X deletes a triple should the listener at Y be notified? I have been thinking about adding a queue based (JMS 1.1?) listener implementation so that distributed system would be notified of changes from remote systems. The second question deals with reasoners. If the reasoners are using the distributed graph store then I don't think there is an issue so perhaps this one goes away but..... Reasoners do not like it (don't respond to) data that is written into the graph behind the scenes. In a distributed environment does it make sense to somehow utilize the graph listen messages (as noted above) to fire update rules? Are there other issues that I have missed? -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
