Hi again, I have an idea that *maybe* can serve as a base for our development. Our system stores a huge number of objects, that are exchanged as XML files. All nodes can create and update objects that where created on other nodes.
If we had any warranty that all nodes will always be online, the solution could probably be: 1) when a node creates a new object it publishes it as a Updateable Subspace Key and becomes responsible for the versioning of the object. The same versioning gives us an online history of the object. 2) all objects publish a subscription file that can be used to say whether they are interested in any other object or not. 3) on creating/updating an object the publisher node effects a search that identifies the nodes that are interested in receiving it 4) the object fremails these node the updated version 5) on updating an object that it does not maintain (i.e. that was created on other node, that is maintaining it on the net) a node fremails the updated version to the maintaining node. This node accpets the version, publishes the updated object edition and proceeds to inform all interested parties. Could such a model work? And how can we cope with the fact that very often the maintainer node will be down? Thanks in advance Berto -- ============================== Constitution du 24 juin 1793 - Article 35. - Quand le gouvernement viole les droits du peuple, l'insurrection est, pour le peuple et pour chaque portion du peuple, le plus sacr? des droits et le plus indispensable des devoirs. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20090310/b88f19f5/attachment.html>
