[Dev] Existing p2p systems for getting offline node back up to date?

[Bill Seitz]

If the focus is on getting semi-frequently updated small datasets (e.g. 
contact info, free/busy calendar availability), then maybe simpler hacks 
make more sense.

Also note that we are expecting each user to have an account on an email 
server. And once could argue that it's not unreasonable to expect people 
to have an IMAP email account.

I ran across a protocol that's related to IMAP for storing configuration 
and presence info, called ACAP.

http://webseitz.fluxent.com/wiki/ACAP
http://asg.web.cmu.edu/acap/

Ray Ryan wrote:

> This is an excerpt from a discussion on the Design list.  
> <http://lists.osafoundation.org/pipermail/design/2002-November/ 
> 000896.html>
>
> On Monday, November 11, 2002, at 02:36  PM, Jeremy Hylton wrote:
>
>>>>>>> "MCF" == Mike C Fletcher <mcfletch@rogers.com> writes:
>>>>>>
>>
>>   MCF> Regarding peer-to-peer sharing: There are a number of
>>   MCF> message-passing system (Spread and the like) which support
>>   MCF> synchronisation with hosts which may be offline at the moment
>>   MCF> the message is sent (without a centralised server).
>>
>> Spread is not such a system.  Spread will deliver a message to every
>> current group member and provides a variety of reliability
>> guarantees.  In all cases, a message is delivered to currently active
>> group members.  It does not store messages.
>>
>> Spread is a very nice package, regardless.
>
>
> If Spread doesn't support this kind of thing (catching up on messages  
> delivered while offline, or otherwise getting back in sync), what does?
>
> Ray
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev
>
>
>