[Spread-users] Daemon deleting client's un-forwarded messages onclient disconnect?

[John Lane Schultz]

I'm not 100% sure about any such short circuits in Spread.  

I assumed the group you were sending your application messages to was a
regular group that your receiver joined.  So long as you send your final
"finish" message to both a regular group and to your own private group (and
wait for it to deliver) then that should ensure none of your messages are
dropped by the daemon.

Cheers!

---
John Lane Schultz
Spread Concepts LLC
Phn: 443 838 2200 

-----Original Message-----
From: Daniel Marques [mailto:marques77 at gmail.com] 
Sent: Friday, June 13, 2008 3:39 PM
To: John Lane Schultz
Cc: spread-users at lists.spread.org
Subject: Re: [Spread-users] Daemon deleting client's un-forwarded messages
onclient disconnect?

John,

Actually, the reason I described my solution in terms of the private
groups is that I was wondering about the "short circuits" that Spread
might have in place.

Generally, will a daemon forward a message to another daemon if it
knows that none of the second daemon's clients belong to any of the
groups that the message was sent to?

Thanks.

Dan



On Fri, Jun 13, 2008 at 2:12 PM, John Lane Schultz
<jschultz at spreadconcepts.com> wrote:
> Yes, what you propose should give you exactly what you want.  Just to be
> safe though, I would simply send the final real message to both the
> recipient and the sender.  This will ensure that no short circuits are
> invoked (e.g. - sending to your own private group might go on a different
> path than normal messages).
>
> Cheers!
>
> ---
> John Lane Schultz
> Spread Concepts LLC
> Phn: 443 838 2200
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 5052 bytes
Desc: not available
Url : http://lists.spread.org/pipermail/spread-users/attachments/20080613/df33d8bd/attachment.bin