JXTA User List, What about Jakarta Slide? Slide has configurable/custom "Stores" that could be configured to be JXTA peers so two Slide instances could synchronize content via JXTA, and a JXTAWebDAV client could work with any WebDAV repository not just Slide.
Ollie On Thu, 2004-02-12 at 09:35, James Todd wrote: > When I thought about this problem domain awhile back my thought was to > take the Java version of subversion[.tigris.org] and see about swapping > out the low level transports in favor of (the ultra cool) > JxtaSocket/JxtaServerSocket > > hth, > > - james > > Summers . Paul wrote: > > Martin, > > > > I've been contemplating such a project myself for the past few days. I'm very new > > to JXTA and am trying to learn the ins and outs but that was a project I was > > thinking of pursuing. I think the one tough hurdle is where the base source would > > be stored or if it was distributed across peers, how would users be sure they had > > the most updated version if a particular user was not connected to the peer group > > at a given time? One solution I considered was to make a particular peer a project > > head for a given project. So, the master source would be stored with them and all > > check-ins/outs would go through them but different projects could have different > > heads. So, Peer A could project head of project 1 but Peer B project head of > > project 2. That was just one idea. > > > > Any other thoughts?? > > > > Paul > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
