<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>RE: [Spread-users] Spread usage scenario for sending data</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>> From: Ryan Caudy</FONT>
</P>
<P><FONT SIZE=2>> >(Ignore possible </FONT>
<BR><FONT SIZE=2>> > conflicts for the purposes of this explanation.)</FONT>
<BR><FONT SIZE=2>> ></FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Maybe you have some sort of special data semantics, like commutative </FONT>
<BR><FONT SIZE=2>> updates... otherwise, the amount of complexity being ignored </FONT>
<BR><FONT SIZE=2>> is fairly </FONT>
<BR><FONT SIZE=2>> significant.</FONT>
</P>
<P><FONT SIZE=2>Agreed, but it's not a problem that Spread addresses. Since I'm asking about Spread, I ignored extraneous detail, however complex.</FONT></P>
<P><FONT SIZE=2>> Reliable for Spread means the same thing as reliable for </FONT>
<BR><FONT SIZE=2>> other network </FONT>
<BR><FONT SIZE=2>> protocols... if a message (UDP) is lost, it will be resent </FONT>
<BR><FONT SIZE=2>> until it does </FONT>
<BR><FONT SIZE=2>> arrive.</FONT>
</P>
<P><FONT SIZE=2>Understood.</FONT>
</P>
<P><FONT SIZE=2>> You haven't really discussed your network architecture, but </FONT>
<BR><FONT SIZE=2>> Spread isn't </FONT>
<BR><FONT SIZE=2>> really designed to help centralized client/server systems, </FONT>
<BR><FONT SIZE=2>> assuming you </FONT>
<BR><FONT SIZE=2>> have a good, switched network. For you, (unless you need higher </FONT>
<BR><FONT SIZE=2>> service types than FIFO) all you gain over TCP is ease of </FONT>
<BR><FONT SIZE=2>> implementation, which may not help if you have trouble </FONT>
<BR><FONT SIZE=2>> learning to use </FONT>
<BR><FONT SIZE=2>> Spread. Spread's design would show more of its potential in a system </FONT>
<BR><FONT SIZE=2>> with multiple databases acting as peers, rather than this 1 </FONT>
<BR><FONT SIZE=2>> master/many </FONT>
<BR><FONT SIZE=2>> slaves design.</FONT>
</P>
<P><FONT SIZE=2>So Spread isn't a good fit for this problem. Thanks for the explanation.</FONT>
</P>
<P><FONT SIZE=2>It would be helpful for future researchers if the Spread documentation defined "reliability" in the Spread context. The documentation says that Spread is reliable, but doesn't actually say what that means, which is why I had to ask the list.</FONT></P>
<P><FONT SIZE=2>Thanks again for your response.</FONT>
</P>
<P><FONT SIZE=2>PJDM</FONT>
<BR><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Peter Mayne</FONT>
<BR><FONT SIZE=2>Technology Consultant</FONT>
<BR><FONT SIZE=2>Spherion Technology Solutions</FONT>
<BR><FONT SIZE=2>Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602</FONT>
<BR><FONT SIZE=2>T: 61 2 62689727 F: 61 2 62689777</FONT>
</P>
</BODY>
<!--[object_id=#ap.spherion.com#]--><P align=left><FONT face=Tahoma size=2></FONT> <FONT size=1>The information contained in this email and any attachments to it:</FONT></P>
<P align=left><FONT size=1>(a) may be confidential and if you are not the intended recipient, any interference with, <BR>use, disclosure or copying of this material is unauthorised and prohibited; and</FONT></P>
<P align=left><FONT size=1>(b) may contain personal information of the recipient and/or the sender as defined <BR>under the Privacy Act 1988 (Cth). Consent is hereby given by the recipient(s) to <BR>collect, hold and use such information and any personal information contained in a <BR>response to this email, for any reasonable purpose in the ordinary course of <BR>Spherion's <BR>business, including forwarding this email internally or disclosing it to a third party. All <BR>personal information collected by Spherion will be handled in accordance with <BR>Spherion's Privacy Policy. If you have received this email in error, please notify the <BR>sender and delete it.</FONT></P>
<P align=left><FONT size=1>(c) you agree not to employ or arrange employment for any candidate(s) supplied in <BR>this email and any attachments without first entering into a contractual agreement with <BR>Spherion. You further agree not to divulge any information contained in this document <BR>to any person(s) or entities without the express permission of Spherion.<BR></FONT></P>
<P align=left><FONT face=Tahoma size=2><FONT color=#0000ff><BR> </P></FONT></FONT></HTML>