Re: [xwiki-users] state of xwiki concerto

Have you changed your view on P2P operations yet? It would seem that for replication (including targeted, partial replications), scalability, and offline operations, P2P would be a good way to manage this for an enterprise class wiki. As a matter of interest, your three use cases for Concerto: (1) massive collaboration where pages can be edited by large numbers of people, similarly to Wikipedia; (2) disconnected work where any participating node should continue offering the Wiki, including update functionality; and (3) opportunistic collaboration where a set of disconnected nodes should be able to create on-the-fly ad-hoc networks by connecting themselves seems to be very relevant in areas where consistent network communications is not always a given. If Concerto is not a reasonable approach to this, what would you suggest? I need full write access to the replicated wiki instances, and those changes need to propagate through the network as soon as connectivity becomes available. But it also needs to be smart - where I might only want to replicate data that is specific to my projects (say in a world-wide development project), perhaps in specific Spaces. Would appreciate your thoughts! Thank you, Mike -- View this message in context: http://xwiki.475771.n2.nabble.com/state-of-xwiki-concerto-tp5239336p7583238… Sent from the XWiki- Users mailing list archive at Nabble.com.