<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_06_30_1617227</id>
	<title>Guaranteed Transmission Protocols For Windows?</title>
	<author>timothy</author>
	<datestamp>1246379400000</datestamp>
	<htmltext><a href="http://www.nitrogen.za.org/" rel="nofollow">Michael</a> writes <i>"Part of our business at my work involves transferring mission critical files across a 2 mbit microwave connection, into a government-run telecommunications center with a very dodgy internal network and then finally to our own server inside the center. The computers at both ends run Windows. What sort of protocols or tools are available to me that will guarantee to get the data transferred across better than a straight Windows file system copy? Since before I started working here, they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals."</i></htmltext>
<tokenext>Michael writes " Part of our business at my work involves transferring mission critical files across a 2 mbit microwave connection , into a government-run telecommunications center with a very dodgy internal network and then finally to our own server inside the center .
The computers at both ends run Windows .
What sort of protocols or tools are available to me that will guarantee to get the data transferred across better than a straight Windows file system copy ?
Since before I started working here , they 've been using FTP to upload the files , but many times the copied files are a few kilobytes smaller than the originals .
"</tokentext>
<sentencetext>Michael writes "Part of our business at my work involves transferring mission critical files across a 2 mbit microwave connection, into a government-run telecommunications center with a very dodgy internal network and then finally to our own server inside the center.
The computers at both ends run Windows.
What sort of protocols or tools are available to me that will guarantee to get the data transferred across better than a straight Windows file system copy?
Since before I started working here, they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530787</id>
	<title>Re:Two words:</title>
	<author>godrik</author>
	<datestamp>1246384740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>hey, that's three words!<nobr> <wbr></nobr>:)</htmltext>
<tokenext>hey , that 's three words !
: )</tokentext>
<sentencetext>hey, that's three words!
:)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530595</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532001</id>
	<title>Most likely...</title>
	<author>kylemonger</author>
	<datestamp>1246388400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>... this isn't a file copying problem, but rather a verification problem.  If a file sometimes winds a few KB short could it be that someone or some process at the destination grabbed the file before it finished copying?  If that is what's happening then any file copying protocol that copies the file to a temp location and then links the file into place at completion would solve this problem.</htmltext>
<tokenext>... this is n't a file copying problem , but rather a verification problem .
If a file sometimes winds a few KB short could it be that someone or some process at the destination grabbed the file before it finished copying ?
If that is what 's happening then any file copying protocol that copies the file to a temp location and then links the file into place at completion would solve this problem .</tokentext>
<sentencetext>... this isn't a file copying problem, but rather a verification problem.
If a file sometimes winds a few KB short could it be that someone or some process at the destination grabbed the file before it finished copying?
If that is what's happening then any file copying protocol that copies the file to a temp location and then links the file into place at completion would solve this problem.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28602301</id>
	<title>Kermit is your friend</title>
	<author>gimme00</author>
	<datestamp>1246888200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Kermit is your friend.  You could also use zmodem with sliding windows<nobr> <wbr></nobr>:)</htmltext>
<tokenext>Kermit is your friend .
You could also use zmodem with sliding windows : )</tokentext>
<sentencetext>Kermit is your friend.
You could also use zmodem with sliding windows :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531829</id>
	<title>Re:Correct me if I'm wrong...</title>
	<author>SuiteSisterMary</author>
	<datestamp>1246387740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>TCP only guarantees that it will tell you if it fails.  It has no way of guaranteeing 'delivery.'</p><p>For all we know, he's scripted ftp.exe and isn't checking the exit codes, and it could be quite merrily telling him that it's never worked properly.</p></htmltext>
<tokenext>TCP only guarantees that it will tell you if it fails .
It has no way of guaranteeing 'delivery .
'For all we know , he 's scripted ftp.exe and is n't checking the exit codes , and it could be quite merrily telling him that it 's never worked properly .</tokentext>
<sentencetext>TCP only guarantees that it will tell you if it fails.
It has no way of guaranteeing 'delivery.
'For all we know, he's scripted ftp.exe and isn't checking the exit codes, and it could be quite merrily telling him that it's never worked properly.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536871</id>
	<title>old skool solution</title>
	<author>Anonymous</author>
	<datestamp>1246367820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Zmodem baby.  Restartable transfers, auto-start by the sender, an expanded 32-bit CRC, and control character quoting.  Just make sure you have a 16550 UART.</p></htmltext>
<tokenext>Zmodem baby .
Restartable transfers , auto-start by the sender , an expanded 32-bit CRC , and control character quoting .
Just make sure you have a 16550 UART .</tokentext>
<sentencetext>Zmodem baby.
Restartable transfers, auto-start by the sender, an expanded 32-bit CRC, and control character quoting.
Just make sure you have a 16550 UART.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532693</id>
	<title>Re:TCP?</title>
	<author>adamstew</author>
	<datestamp>1246390740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>In NTFS, you can specify the block size when you format the disk.</p></htmltext>
<tokenext>In NTFS , you can specify the block size when you format the disk .</tokentext>
<sentencetext>In NTFS, you can specify the block size when you format the disk.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531833</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534731</id>
	<title>PAR2</title>
	<author>Anonymous</author>
	<datestamp>1246356000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Par2 while not a transmission protocol provides forward error correction and validation and should prevent the need to retransmit files when corrupted in transit.</p></htmltext>
<tokenext>Par2 while not a transmission protocol provides forward error correction and validation and should prevent the need to retransmit files when corrupted in transit .</tokentext>
<sentencetext>Par2 while not a transmission protocol provides forward error correction and validation and should prevent the need to retransmit files when corrupted in transit.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530163</id>
	<title>Jesus protocol</title>
	<author>Anonymous</author>
	<datestamp>1246383180000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>Jesus is awesome.</p></htmltext>
<tokenext>Jesus is awesome .</tokentext>
<sentencetext>Jesus is awesome.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530943</id>
	<title>Re:Guaranteed?</title>
	<author>jeffmeden</author>
	<datestamp>1246385100000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>You forgot a few:
<br> <br>
Windows at both ends...  Used to use FTP...  Considering windows file sharing...
<br> <br>
Is anyone else a little nervous?  I hope by 'government' he means Department of Natural Resources or some equally uninteresting entity.  I am picturing someone at the SEC going "You know, I swear this accounting data had a few more rows the last time I looked at it-- Oh well it's not like this Madoff guy is actually up to anything strange anyway"</htmltext>
<tokenext>You forgot a few : Windows at both ends... Used to use FTP... Considering windows file sharing.. . Is anyone else a little nervous ?
I hope by 'government ' he means Department of Natural Resources or some equally uninteresting entity .
I am picturing someone at the SEC going " You know , I swear this accounting data had a few more rows the last time I looked at it-- Oh well it 's not like this Madoff guy is actually up to anything strange anyway "</tokentext>
<sentencetext>You forgot a few:
 
Windows at both ends...  Used to use FTP...  Considering windows file sharing...
 
Is anyone else a little nervous?
I hope by 'government' he means Department of Natural Resources or some equally uninteresting entity.
I am picturing someone at the SEC going "You know, I swear this accounting data had a few more rows the last time I looked at it-- Oh well it's not like this Madoff guy is actually up to anything strange anyway"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532637</id>
	<title>Blast</title>
	<author>Anonymous</author>
	<datestamp>1246390500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Look for a very old communications package from what used to be  Communications Research Group, later was Blast, Inc - and somewhere in between I think was owned by U.S. Robotics.</p><p>Anyway, the software package was called "Blast", and it had a file transfer protocol that ran over modems and TCP/IP.</p><p>If the file transfer completed, the file was *guaranteed* to be correct on the recipient's side.<br>
&nbsp;</p></htmltext>
<tokenext>Look for a very old communications package from what used to be Communications Research Group , later was Blast , Inc - and somewhere in between I think was owned by U.S. Robotics.Anyway , the software package was called " Blast " , and it had a file transfer protocol that ran over modems and TCP/IP.If the file transfer completed , the file was * guaranteed * to be correct on the recipient 's side .
 </tokentext>
<sentencetext>Look for a very old communications package from what used to be  Communications Research Group, later was Blast, Inc - and somewhere in between I think was owned by U.S. Robotics.Anyway, the software package was called "Blast", and it had a file transfer protocol that ran over modems and TCP/IP.If the file transfer completed, the file was *guaranteed* to be correct on the recipient's side.
 </sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530861</id>
	<title>a great program</title>
	<author>ILuvRamen</author>
	<datestamp>1246384800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Leechget is a cool program for this.  I think it does data verification during or at the end of the download and supports pausing and resuming.  It is primarily a download accelerator/manager but it also installs a right click context menu of "copy here using leechget" for all local file transfers.  So go that over the network and you'll not only get it there correctly but it'll go at max speed because it opens multiple connections at once and sends parts of the file then re-joins them.</htmltext>
<tokenext>Leechget is a cool program for this .
I think it does data verification during or at the end of the download and supports pausing and resuming .
It is primarily a download accelerator/manager but it also installs a right click context menu of " copy here using leechget " for all local file transfers .
So go that over the network and you 'll not only get it there correctly but it 'll go at max speed because it opens multiple connections at once and sends parts of the file then re-joins them .</tokentext>
<sentencetext>Leechget is a cool program for this.
I think it does data verification during or at the end of the download and supports pausing and resuming.
It is primarily a download accelerator/manager but it also installs a right click context menu of "copy here using leechget" for all local file transfers.
So go that over the network and you'll not only get it there correctly but it'll go at max speed because it opens multiple connections at once and sends parts of the file then re-joins them.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530967</id>
	<title>Re:Two words:</title>
	<author>Anonymous</author>
	<datestamp>1246385160000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>DVD burner, FedEx.</p></div><p>I'm no mathematician, but isn't that 3 words?</p></div>
	</htmltext>
<tokenext>DVD burner , FedEx.I 'm no mathematician , but is n't that 3 words ?</tokentext>
<sentencetext>DVD burner, FedEx.I'm no mathematician, but isn't that 3 words?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530595</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532125</id>
	<title>Re:TCP?</title>
	<author>geekoid</author>
	<datestamp>1246388760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yep. Or he has no clue about the Windows file system, specifically block size allocations.</p></htmltext>
<tokenext>Yep .
Or he has no clue about the Windows file system , specifically block size allocations .</tokentext>
<sentencetext>Yep.
Or he has no clue about the Windows file system, specifically block size allocations.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534227</id>
	<title>Re:Correct me if I'm wrong...</title>
	<author>Bacon Bits</author>
	<datestamp>1246354080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>TCP guarantees that the data transmitted by one host is the same data received by another host.  It does not guarantee that the data stored at one host is the data stored at the second host.  TCP is Transport Layer to Transport Layer integrity.  That's insufficient when you're required to guarantee Application to Application integrity, or disk to disk integrity.  This is part of the problem we fact with HIPAA electronic medical record transfers.  There is no generic, universal, open, secure method to ensure data transport from one disk to another.  Most transport methods only care about host-to-host, and that's simply not sufficient.  Assuming there are no errors from NIC to disk isn't good enough.  Such a system would need an integrity check at sending host, transfer, and an integrity check at the receiving host.</p><p>Several commercial FTP/SFTP programs provide extensions that allow you to run integrity checks:<br>Vandyke Software SecureFX<br>GlobalSCAPE EFT Server</p><p>I've not set up either, but they're both designed around the demands of HIPAA.</p><p>The simplest way to do things is to ZIP the files before you send them and then test the ZIP file on the receiving end, but that's fairly manual and is only as good as the algorithm involved: CRC-32.  Good enough for most applications but not sufficient for many more.</p></htmltext>
<tokenext>TCP guarantees that the data transmitted by one host is the same data received by another host .
It does not guarantee that the data stored at one host is the data stored at the second host .
TCP is Transport Layer to Transport Layer integrity .
That 's insufficient when you 're required to guarantee Application to Application integrity , or disk to disk integrity .
This is part of the problem we fact with HIPAA electronic medical record transfers .
There is no generic , universal , open , secure method to ensure data transport from one disk to another .
Most transport methods only care about host-to-host , and that 's simply not sufficient .
Assuming there are no errors from NIC to disk is n't good enough .
Such a system would need an integrity check at sending host , transfer , and an integrity check at the receiving host.Several commercial FTP/SFTP programs provide extensions that allow you to run integrity checks : Vandyke Software SecureFXGlobalSCAPE EFT ServerI 've not set up either , but they 're both designed around the demands of HIPAA.The simplest way to do things is to ZIP the files before you send them and then test the ZIP file on the receiving end , but that 's fairly manual and is only as good as the algorithm involved : CRC-32 .
Good enough for most applications but not sufficient for many more .</tokentext>
<sentencetext>TCP guarantees that the data transmitted by one host is the same data received by another host.
It does not guarantee that the data stored at one host is the data stored at the second host.
TCP is Transport Layer to Transport Layer integrity.
That's insufficient when you're required to guarantee Application to Application integrity, or disk to disk integrity.
This is part of the problem we fact with HIPAA electronic medical record transfers.
There is no generic, universal, open, secure method to ensure data transport from one disk to another.
Most transport methods only care about host-to-host, and that's simply not sufficient.
Assuming there are no errors from NIC to disk isn't good enough.
Such a system would need an integrity check at sending host, transfer, and an integrity check at the receiving host.Several commercial FTP/SFTP programs provide extensions that allow you to run integrity checks:Vandyke Software SecureFXGlobalSCAPE EFT ServerI've not set up either, but they're both designed around the demands of HIPAA.The simplest way to do things is to ZIP the files before you send them and then test the ZIP file on the receiving end, but that's fairly manual and is only as good as the algorithm involved: CRC-32.
Good enough for most applications but not sufficient for many more.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531933</id>
	<title>Think outside the box?</title>
	<author>node159</author>
	<datestamp>1246388100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Maybe think outside the box for a second and really look at what you are asking...</p><p>You plan to transfer \_mission critical files\_ over an unreliable link. Maybe you should provide a \_mission critical link\_? You know, a leased line with a backup? If you can't justify the cost, it probably isn't mission critical.</p><p>The right tools for the job people... Jez!</p></htmltext>
<tokenext>Maybe think outside the box for a second and really look at what you are asking...You plan to transfer \ _mission critical files \ _ over an unreliable link .
Maybe you should provide a \ _mission critical link \ _ ?
You know , a leased line with a backup ?
If you ca n't justify the cost , it probably is n't mission critical.The right tools for the job people... Jez !</tokentext>
<sentencetext>Maybe think outside the box for a second and really look at what you are asking...You plan to transfer \_mission critical files\_ over an unreliable link.
Maybe you should provide a \_mission critical link\_?
You know, a leased line with a backup?
If you can't justify the cost, it probably isn't mission critical.The right tools for the job people... Jez!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530737</id>
	<title>biznAtch</title>
	<author>Anonymous</author>
	<datestamp>1246384620000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext>but with Net3raft their parting</htmltext>
<tokenext>but with Net3raft their parting</tokentext>
<sentencetext>but with Net3raft their parting</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539553</id>
	<title>Re:Any encrypted transmission protocol actually</title>
	<author>Anonymous</author>
	<datestamp>1246481940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Is there is also a reason that the files could be showing as a few KB smaller when they arrive at the other side, even though any file transfer protocol used will have sent a complete intact version of the file?  Admittedly, it's a bit obscure. But how would having large clusters on the source disk and small clusters on the target disk result in an apparent varying shrink in filesize for different files?</p></htmltext>
<tokenext>Is there is also a reason that the files could be showing as a few KB smaller when they arrive at the other side , even though any file transfer protocol used will have sent a complete intact version of the file ?
Admittedly , it 's a bit obscure .
But how would having large clusters on the source disk and small clusters on the target disk result in an apparent varying shrink in filesize for different files ?</tokentext>
<sentencetext>Is there is also a reason that the files could be showing as a few KB smaller when they arrive at the other side, even though any file transfer protocol used will have sent a complete intact version of the file?
Admittedly, it's a bit obscure.
But how would having large clusters on the source disk and small clusters on the target disk result in an apparent varying shrink in filesize for different files?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530645</id>
	<title>Re:RTFM - set binary mode in FTP</title>
	<author>Anonymous</author>
	<datestamp>1246384380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>I never knew that law had a name, sweet.  I do find that many people who do not work with technology, are not engineers, or just dont work in the field, tend to almost always blame the tool first.  I've never understood this thinking since the obvious jump would be; this obviously work for many many other people so why not me, I must be the problem</htmltext>
<tokenext>I never knew that law had a name , sweet .
I do find that many people who do not work with technology , are not engineers , or just dont work in the field , tend to almost always blame the tool first .
I 've never understood this thinking since the obvious jump would be ; this obviously work for many many other people so why not me , I must be the problem</tokentext>
<sentencetext>I never knew that law had a name, sweet.
I do find that many people who do not work with technology, are not engineers, or just dont work in the field, tend to almost always blame the tool first.
I've never understood this thinking since the obvious jump would be; this obviously work for many many other people so why not me, I must be the problem</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</id>
	<title>Re:TCP?</title>
	<author>AvitarX</author>
	<datestamp>1246383600000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>I bet it is file systems with different block sizes rounding slightly differently, and an OP that does not understand.</p></htmltext>
<tokenext>I bet it is file systems with different block sizes rounding slightly differently , and an OP that does not understand .</tokentext>
<sentencetext>I bet it is file systems with different block sizes rounding slightly differently, and an OP that does not understand.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539563</id>
	<title>Reasons why people still use Connect:Direct</title>
	<author>chiark</author>
	<datestamp>1246438800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If it's truly mission critical (and if it is, it sounds like your mission is in real danger if you keep dropping bytes!), you could do worse than look at Connect:Direct from Sterling Software.  It's the standard transmission software for bits of the core financial transaction world in the UK and with good reason.</p><p>Sure it's "only" a secure transmission and there's plenty of free alternatives, but this is one time when I would recommend paying out for the certainty you need...  Others will no doubt disagree, but having used a variety of things for mission critical file transmission, C:D is a safe choice.</p></htmltext>
<tokenext>If it 's truly mission critical ( and if it is , it sounds like your mission is in real danger if you keep dropping bytes !
) , you could do worse than look at Connect : Direct from Sterling Software .
It 's the standard transmission software for bits of the core financial transaction world in the UK and with good reason.Sure it 's " only " a secure transmission and there 's plenty of free alternatives , but this is one time when I would recommend paying out for the certainty you need... Others will no doubt disagree , but having used a variety of things for mission critical file transmission , C : D is a safe choice .</tokentext>
<sentencetext>If it's truly mission critical (and if it is, it sounds like your mission is in real danger if you keep dropping bytes!
), you could do worse than look at Connect:Direct from Sterling Software.
It's the standard transmission software for bits of the core financial transaction world in the UK and with good reason.Sure it's "only" a secure transmission and there's plenty of free alternatives, but this is one time when I would recommend paying out for the certainty you need...  Others will no doubt disagree, but having used a variety of things for mission critical file transmission, C:D is a safe choice.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531277</id>
	<title>Re:Line endings!</title>
	<author>bwcbwc</author>
	<datestamp>1246386000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Except OP says he's going from Windows to Windows. So unless the FTP server is configured to respond with a system type as Unix, that doesn't really fly.</p><p>Send the $20 to the EFF.</p></htmltext>
<tokenext>Except OP says he 's going from Windows to Windows .
So unless the FTP server is configured to respond with a system type as Unix , that does n't really fly.Send the $ 20 to the EFF .</tokentext>
<sentencetext>Except OP says he's going from Windows to Windows.
So unless the FTP server is configured to respond with a system type as Unix, that doesn't really fly.Send the $20 to the EFF.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531833</id>
	<title>Re:TCP?</title>
	<author>bertoelcon</author>
	<datestamp>1246387800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I bet it is file systems with different block sizes rounding slightly differently, and an OP that does not understand.</p></div><p>But the computers on both ends are running Windows, even if it is FAT32 and NTFS is this really a possible outcome?</p></div>
	</htmltext>
<tokenext>I bet it is file systems with different block sizes rounding slightly differently , and an OP that does not understand.But the computers on both ends are running Windows , even if it is FAT32 and NTFS is this really a possible outcome ?</tokentext>
<sentencetext>I bet it is file systems with different block sizes rounding slightly differently, and an OP that does not understand.But the computers on both ends are running Windows, even if it is FAT32 and NTFS is this really a possible outcome?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536719</id>
	<title>DTN</title>
	<author>usman\_ismail</author>
	<datestamp>1246366680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>You need a Disruption Tolerant Network (DTN) solution, there is no commercial DTN's out there that I know off but the DAKNet people at MIT were working on something and a group a U of Waterloo has an implementation.

<a href="http://www.firstmilesolutions.com/" title="firstmilesolutions.com" rel="nofollow">http://www.firstmilesolutions.com/</a> [firstmilesolutions.com]
<a href="http://blizzard.cs.uwaterloo.ca/tetherless/index.php/KioskNet" title="uwaterloo.ca" rel="nofollow">http://blizzard.cs.uwaterloo.ca/tetherless/index.php/KioskNet</a> [uwaterloo.ca]</htmltext>
<tokenext>You need a Disruption Tolerant Network ( DTN ) solution , there is no commercial DTN 's out there that I know off but the DAKNet people at MIT were working on something and a group a U of Waterloo has an implementation .
http : //www.firstmilesolutions.com/ [ firstmilesolutions.com ] http : //blizzard.cs.uwaterloo.ca/tetherless/index.php/KioskNet [ uwaterloo.ca ]</tokentext>
<sentencetext>You need a Disruption Tolerant Network (DTN) solution, there is no commercial DTN's out there that I know off but the DAKNet people at MIT were working on something and a group a U of Waterloo has an implementation.
http://www.firstmilesolutions.com/ [firstmilesolutions.com]
http://blizzard.cs.uwaterloo.ca/tetherless/index.php/KioskNet [uwaterloo.ca]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538987</id>
	<title>look into using XTP</title>
	<author>mejustme</author>
	<datestamp>1246388160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>See XTP:  <a href="http://en.wikipedia.org/wiki/Xpress\_Transport\_Protocol" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Xpress\_Transport\_Protocol</a> [wikipedia.org]
Devices that use XTP to help transfer files over satellite links exist.  For example:  Mentat/Packeteer/Blucoat's SkyX product.

(Disclaimer:  I used to work for Packeteer, though not on the SkyX product.)</htmltext>
<tokenext>See XTP : http : //en.wikipedia.org/wiki/Xpress \ _Transport \ _Protocol [ wikipedia.org ] Devices that use XTP to help transfer files over satellite links exist .
For example : Mentat/Packeteer/Blucoat 's SkyX product .
( Disclaimer : I used to work for Packeteer , though not on the SkyX product .
)</tokentext>
<sentencetext>See XTP:  http://en.wikipedia.org/wiki/Xpress\_Transport\_Protocol [wikipedia.org]
Devices that use XTP to help transfer files over satellite links exist.
For example:  Mentat/Packeteer/Blucoat's SkyX product.
(Disclaimer:  I used to work for Packeteer, though not on the SkyX product.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530939</id>
	<title>Re:Guaranteed?  Wait, What!?</title>
	<author>Culture20</author>
	<datestamp>1246385040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>mission critical files<nobr> <wbr></nobr>... microwave connection<nobr> <wbr></nobr>... government<br>
They use FTP?  Hopefully only through ipsec or something.</htmltext>
<tokenext>mission critical files ... microwave connection ... government They use FTP ?
Hopefully only through ipsec or something .</tokentext>
<sentencetext>mission critical files ... microwave connection ... government
They use FTP?
Hopefully only through ipsec or something.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532301</id>
	<title>Re:PAR2?</title>
	<author>overlordofmu</author>
	<datestamp>1246389420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I cannot believe this excellent suggestion is so far down the list in the responses.<br> <br>
I think the combination of SFTP and PAR2 is a effective, simple answer.</htmltext>
<tokenext>I can not believe this excellent suggestion is so far down the list in the responses .
I think the combination of SFTP and PAR2 is a effective , simple answer .</tokentext>
<sentencetext>I cannot believe this excellent suggestion is so far down the list in the responses.
I think the combination of SFTP and PAR2 is a effective, simple answer.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531293</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533281</id>
	<title>Re:TCP?</title>
	<author>camperdave</author>
	<datestamp>1246393260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Thanks for the explanation.  I've always been curious about that myself (but not actually curious enough to seek out the answer).  People tend to forget that there were computers around before Windows was invented, and that ASCII is a code for data transmission (information interchange), not internal storage. It uses 7 bit characters, not 8, and has a rich array of record management and data flow characters.</htmltext>
<tokenext>Thanks for the explanation .
I 've always been curious about that myself ( but not actually curious enough to seek out the answer ) .
People tend to forget that there were computers around before Windows was invented , and that ASCII is a code for data transmission ( information interchange ) , not internal storage .
It uses 7 bit characters , not 8 , and has a rich array of record management and data flow characters .</tokentext>
<sentencetext>Thanks for the explanation.
I've always been curious about that myself (but not actually curious enough to seek out the answer).
People tend to forget that there were computers around before Windows was invented, and that ASCII is a code for data transmission (information interchange), not internal storage.
It uses 7 bit characters, not 8, and has a rich array of record management and data flow characters.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538641</id>
	<title>Re:Any encrypted transmission protocol actually</title>
	<author>shiftless</author>
	<datestamp>1246383960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And what the hell is wrong with FTP? It's a very fast, convenient, widely supported, relatively reliable way to transfer files from one place to another.</p></htmltext>
<tokenext>And what the hell is wrong with FTP ?
It 's a very fast , convenient , widely supported , relatively reliable way to transfer files from one place to another .</tokentext>
<sentencetext>And what the hell is wrong with FTP?
It's a very fast, convenient, widely supported, relatively reliable way to transfer files from one place to another.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531201</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531195</id>
	<title>Anonymous Coward</title>
	<author>Anonymous</author>
	<datestamp>1246385760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Is the destination computer hard drive formatted the same as the source hard drive?  If not then this could be as simple as the extra bits for each sector on the drive reporting the correct space for the drive.</p></htmltext>
<tokenext>Is the destination computer hard drive formatted the same as the source hard drive ?
If not then this could be as simple as the extra bits for each sector on the drive reporting the correct space for the drive .</tokentext>
<sentencetext>Is the destination computer hard drive formatted the same as the source hard drive?
If not then this could be as simple as the extra bits for each sector on the drive reporting the correct space for the drive.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532847</id>
	<title>Robocopy is what you want</title>
	<author>toporok</author>
	<datestamp>1246391340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If it's a Windows-Windows, Robocopy is what you want.  It will do everything you need.  It's free too and made for Windows.</htmltext>
<tokenext>If it 's a Windows-Windows , Robocopy is what you want .
It will do everything you need .
It 's free too and made for Windows .</tokentext>
<sentencetext>If it's a Windows-Windows, Robocopy is what you want.
It will do everything you need.
It's free too and made for Windows.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536039</id>
	<title>WAIT!!!</title>
	<author>DRAGONWEEZEL</author>
	<datestamp>1246362960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Am I the only one to question whether there is a real problem?  Did I read it wrong (ADD so it's possible)</p><p>What if the File allocation size is just different on the two drives? Then the exact same file can, and WILL be different sizes on disk, no harm, no foul, but maybe fowl in the way of the transmision route.</p><p>For instance, if you write a 6k file to a HDD w/ a 4096b allocation size, it's going to take up 8k(ish worth of space, despite the file being 6k.</p><p>Now if you write that same file to a system w/ 512b allocation size, that 6k file will take about 6k.</p><p>And it can get smaller by 4-xkb in a situation where a newer system with a larger allocation size is sending a file to a (usually) older system w/ a smaller allocation size.</p><p>Then again, maybe I failed math.  but I thought that's why there's "Size" then "Size on disk"</p></htmltext>
<tokenext>Am I the only one to question whether there is a real problem ?
Did I read it wrong ( ADD so it 's possible ) What if the File allocation size is just different on the two drives ?
Then the exact same file can , and WILL be different sizes on disk , no harm , no foul , but maybe fowl in the way of the transmision route.For instance , if you write a 6k file to a HDD w/ a 4096b allocation size , it 's going to take up 8k ( ish worth of space , despite the file being 6k.Now if you write that same file to a system w/ 512b allocation size , that 6k file will take about 6k.And it can get smaller by 4-xkb in a situation where a newer system with a larger allocation size is sending a file to a ( usually ) older system w/ a smaller allocation size.Then again , maybe I failed math .
but I thought that 's why there 's " Size " then " Size on disk "</tokentext>
<sentencetext>Am I the only one to question whether there is a real problem?
Did I read it wrong (ADD so it's possible)What if the File allocation size is just different on the two drives?
Then the exact same file can, and WILL be different sizes on disk, no harm, no foul, but maybe fowl in the way of the transmision route.For instance, if you write a 6k file to a HDD w/ a 4096b allocation size, it's going to take up 8k(ish worth of space, despite the file being 6k.Now if you write that same file to a system w/ 512b allocation size, that 6k file will take about 6k.And it can get smaller by 4-xkb in a situation where a newer system with a larger allocation size is sending a file to a (usually) older system w/ a smaller allocation size.Then again, maybe I failed math.
but I thought that's why there's "Size" then "Size on disk"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538517</id>
	<title>use NDM</title>
	<author>Anonymous</author>
	<datestamp>1246382280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Look into NDM / Connect:Direct-- ( not the p2p, the software by sterling ). It's what banks and government agencies use to move files between systems. Auto restart, checkpoints during transfer, compression, etc....</p></htmltext>
<tokenext>Look into NDM / Connect : Direct-- ( not the p2p , the software by sterling ) .
It 's what banks and government agencies use to move files between systems .
Auto restart , checkpoints during transfer , compression , etc... .</tokentext>
<sentencetext>Look into NDM / Connect:Direct-- ( not the p2p, the software by sterling ).
It's what banks and government agencies use to move files between systems.
Auto restart, checkpoints during transfer, compression, etc....</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533961</id>
	<title>Re:Correct me if I'm wrong...</title>
	<author>irieken</author>
	<datestamp>1246353000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Wasn't TCP designed for just this?  Guaranteed transmission?</p></div><p>Kind of; it can guarantee transmission via an acknowledgment packet returned to the sender. TCP also includes a CRC checksum that helps weed out bad packets. However, (not 100\% sure about this) the checksum is just a 1 bit flag that is checked against the 1's complement of the payload. This means that it's great if there is just a small error in the transmission, but will result in a false-good packet if there are multiple transmission errors.<br> <br>

The better solution would be to use a protocol that works on TCP or UDP, but has a more robust error detection/correction method. Bittorrent, for example, splits files up into chunks, then creates a 160bit hash of each chunk. Each chunk is compared against the hash upon being recieved, and retransmitted if it does not match. This means that the probability of a malformed chunk being accepted by the bittorrent client is very very very low.</p></div>
	</htmltext>
<tokenext>Was n't TCP designed for just this ?
Guaranteed transmission ? Kind of ; it can guarantee transmission via an acknowledgment packet returned to the sender .
TCP also includes a CRC checksum that helps weed out bad packets .
However , ( not 100 \ % sure about this ) the checksum is just a 1 bit flag that is checked against the 1 's complement of the payload .
This means that it 's great if there is just a small error in the transmission , but will result in a false-good packet if there are multiple transmission errors .
The better solution would be to use a protocol that works on TCP or UDP , but has a more robust error detection/correction method .
Bittorrent , for example , splits files up into chunks , then creates a 160bit hash of each chunk .
Each chunk is compared against the hash upon being recieved , and retransmitted if it does not match .
This means that the probability of a malformed chunk being accepted by the bittorrent client is very very very low .</tokentext>
<sentencetext>Wasn't TCP designed for just this?
Guaranteed transmission?Kind of; it can guarantee transmission via an acknowledgment packet returned to the sender.
TCP also includes a CRC checksum that helps weed out bad packets.
However, (not 100\% sure about this) the checksum is just a 1 bit flag that is checked against the 1's complement of the payload.
This means that it's great if there is just a small error in the transmission, but will result in a false-good packet if there are multiple transmission errors.
The better solution would be to use a protocol that works on TCP or UDP, but has a more robust error detection/correction method.
Bittorrent, for example, splits files up into chunks, then creates a 160bit hash of each chunk.
Each chunk is compared against the hash upon being recieved, and retransmitted if it does not match.
This means that the probability of a malformed chunk being accepted by the bittorrent client is very very very low.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28537427</id>
	<title>Re:TCP?</title>
	<author>sco08y</author>
	<datestamp>1246372260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yeah, the PEBKAC of the people who invented the protocol, and all the other data destroying protocols (SMTP, etc) on the net.</p></htmltext>
<tokenext>Yeah , the PEBKAC of the people who invented the protocol , and all the other data destroying protocols ( SMTP , etc ) on the net .</tokentext>
<sentencetext>Yeah, the PEBKAC of the people who invented the protocol, and all the other data destroying protocols (SMTP, etc) on the net.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531113</id>
	<title>Re:Line endings!</title>
	<author>CrashandDie</author>
	<datestamp>1246385520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's \r\n in Windows and \n in Linux.<br> <br>
<a href="http://en.wikipedia.org/wiki/Newline" title="wikipedia.org" rel="nofollow">Newline</a> [wikipedia.org]</htmltext>
<tokenext>It 's \ r \ n in Windows and \ n in Linux .
Newline [ wikipedia.org ]</tokentext>
<sentencetext>It's \r\n in Windows and \n in Linux.
Newline [wikipedia.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534441</id>
	<title>Both sides Windows, use MSMQ</title>
	<author>Anonymous</author>
	<datestamp>1246354860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Microsoft Message Queue is a guaranteed data delivery service for unreliable networks that can be configured to use encryption and authentication.</p></htmltext>
<tokenext>Microsoft Message Queue is a guaranteed data delivery service for unreliable networks that can be configured to use encryption and authentication .</tokentext>
<sentencetext>Microsoft Message Queue is a guaranteed data delivery service for unreliable networks that can be configured to use encryption and authentication.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531511</id>
	<title>Re:Line endings!</title>
	<author>machine321</author>
	<datestamp>1246386660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It might be line endings, but I'm guessing he's running a batch script via Task Scheduler to call ftp.exe, and he never checks the output or return codes for failure.</p></htmltext>
<tokenext>It might be line endings , but I 'm guessing he 's running a batch script via Task Scheduler to call ftp.exe , and he never checks the output or return codes for failure .</tokentext>
<sentencetext>It might be line endings, but I'm guessing he's running a batch script via Task Scheduler to call ftp.exe, and he never checks the output or return codes for failure.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531387</id>
	<title>Re:UDP.</title>
	<author>Anonymous</author>
	<datestamp>1246386300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>There's something called FilePhile that does UDP scatter-gather transfers, but its not open source.</p><p>http://www.filephile.net/</p></htmltext>
<tokenext>There 's something called FilePhile that does UDP scatter-gather transfers , but its not open source.http : //www.filephile.net/</tokentext>
<sentencetext>There's something called FilePhile that does UDP scatter-gather transfers, but its not open source.http://www.filephile.net/</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542307</id>
	<title>Live Sync or BITS</title>
	<author>Xenophon Fenderson,</author>
	<datestamp>1246463040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>We have similar needs, only we're exchanging files across dodgy Internet connections (e.g., satellite links to sites in the developing world).  Our requirements including operation over low-bandwidth connections and the ability to suspend and resume transfers.  We settled on <a href="https://www.foldershare.com/" title="foldershare.com" rel="nofollow">Windows Live Sync</a> [foldershare.com], since it works on Mac OS X in addition to Windows, and because it required no additional software development effort on our part.  Had Live Sync not been available, we would have developed our own wrapper around BITS.  Because BITS is an extension to HTTP, it degrades gracefully into something interoperable with non-Windows clients.  (BITS would also work over a private network, but that wasn't a feature we required.)</p></htmltext>
<tokenext>We have similar needs , only we 're exchanging files across dodgy Internet connections ( e.g. , satellite links to sites in the developing world ) .
Our requirements including operation over low-bandwidth connections and the ability to suspend and resume transfers .
We settled on Windows Live Sync [ foldershare.com ] , since it works on Mac OS X in addition to Windows , and because it required no additional software development effort on our part .
Had Live Sync not been available , we would have developed our own wrapper around BITS .
Because BITS is an extension to HTTP , it degrades gracefully into something interoperable with non-Windows clients .
( BITS would also work over a private network , but that was n't a feature we required .
)</tokentext>
<sentencetext>We have similar needs, only we're exchanging files across dodgy Internet connections (e.g., satellite links to sites in the developing world).
Our requirements including operation over low-bandwidth connections and the ability to suspend and resume transfers.
We settled on Windows Live Sync [foldershare.com], since it works on Mac OS X in addition to Windows, and because it required no additional software development effort on our part.
Had Live Sync not been available, we would have developed our own wrapper around BITS.
Because BITS is an extension to HTTP, it degrades gracefully into something interoperable with non-Windows clients.
(BITS would also work over a private network, but that wasn't a feature we required.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530399</id>
	<title>rsync</title>
	<author>itsme1234</author>
	<datestamp>1246383720000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>... is what you want. Yes, you can use it with Windows (with or without cygwin bloat). Use -c and a short --timeout and you're good to go. If you're using it over ssh you're looking at three layers of integrity (rsync checksums, ssh and TCP), two of them quite strong even against malicious attacks not only against normal stuff. Put it in a script with a short --timeout; if anything is wrong with the link your ssh session will freeze completely, as soon as your --timeout is reached rsync will die and your script can respawn a new one (which will resume the transfer using whatever chunks with good checksum you have already transfered and will again checksum the whole file when it finishes).</p></htmltext>
<tokenext>... is what you want .
Yes , you can use it with Windows ( with or without cygwin bloat ) .
Use -c and a short --timeout and you 're good to go .
If you 're using it over ssh you 're looking at three layers of integrity ( rsync checksums , ssh and TCP ) , two of them quite strong even against malicious attacks not only against normal stuff .
Put it in a script with a short --timeout ; if anything is wrong with the link your ssh session will freeze completely , as soon as your --timeout is reached rsync will die and your script can respawn a new one ( which will resume the transfer using whatever chunks with good checksum you have already transfered and will again checksum the whole file when it finishes ) .</tokentext>
<sentencetext>... is what you want.
Yes, you can use it with Windows (with or without cygwin bloat).
Use -c and a short --timeout and you're good to go.
If you're using it over ssh you're looking at three layers of integrity (rsync checksums, ssh and TCP), two of them quite strong even against malicious attacks not only against normal stuff.
Put it in a script with a short --timeout; if anything is wrong with the link your ssh session will freeze completely, as soon as your --timeout is reached rsync will die and your script can respawn a new one (which will resume the transfer using whatever chunks with good checksum you have already transfered and will again checksum the whole file when it finishes).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534713</id>
	<title>Re:You're kidding, aren't you??</title>
	<author>Anonymous</author>
	<datestamp>1246355940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>- you have "mission critical files", and the network you're transferring them over is so incredibly badly managed that it doesn't support reliable data transfer</p></div><p>Considering this user's "business" requires him to use a microwave link to a "government" telecommunications center, this is probably the best service available to him and there are no other options.  Actually, a 2Mb circuit by government standards is premium service.  He's lucky he hasn't been rate-limited to 512K.  Mission critical files are transmitted using lower quality media than this every day.</p></div>
	</htmltext>
<tokenext>- you have " mission critical files " , and the network you 're transferring them over is so incredibly badly managed that it does n't support reliable data transferConsidering this user 's " business " requires him to use a microwave link to a " government " telecommunications center , this is probably the best service available to him and there are no other options .
Actually , a 2Mb circuit by government standards is premium service .
He 's lucky he has n't been rate-limited to 512K .
Mission critical files are transmitted using lower quality media than this every day .</tokentext>
<sentencetext>- you have "mission critical files", and the network you're transferring them over is so incredibly badly managed that it doesn't support reliable data transferConsidering this user's "business" requires him to use a microwave link to a "government" telecommunications center, this is probably the best service available to him and there are no other options.
Actually, a 2Mb circuit by government standards is premium service.
He's lucky he hasn't been rate-limited to 512K.
Mission critical files are transmitted using lower quality media than this every day.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534175</id>
	<title>Running</title>
	<author>SlashDev</author>
	<datestamp>1246353780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>a mission critical application under Windows... That in itself is the start of something going bad.

TCP does guarantee transmission.
The actual copy software will have to do some sort of MD5 check at both ends, in order to verify that content was copied properly. I would suggest you write your own copy script, any copy command would work. For government installation, I would suggest an encrypted copy process, scp, sftp, etc...</htmltext>
<tokenext>a mission critical application under Windows... That in itself is the start of something going bad .
TCP does guarantee transmission .
The actual copy software will have to do some sort of MD5 check at both ends , in order to verify that content was copied properly .
I would suggest you write your own copy script , any copy command would work .
For government installation , I would suggest an encrypted copy process , scp , sftp , etc.. .</tokentext>
<sentencetext>a mission critical application under Windows... That in itself is the start of something going bad.
TCP does guarantee transmission.
The actual copy software will have to do some sort of MD5 check at both ends, in order to verify that content was copied properly.
I would suggest you write your own copy script, any copy command would work.
For government installation, I would suggest an encrypted copy process, scp, sftp, etc...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533569</id>
	<title>Re:UDP.</title>
	<author>Anonymous</author>
	<datestamp>1246394640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>UDP is (on its own) not the solution, because when a UDP packet gets lost, there isn't a mechanism in the protocol to let the sender know to retransmit. In this case, they are having packets received that are malformed/missing.</p><p>The actual problem, here, is that FTP relies exclusively on TCP for error detection. TCP's error detection mechanism is extremely simple, and apparently too weak to resist the terrible transmission errors introduced on the second leg of the network.</p><p>Now, if you're not too worried about overhead, Bittorrent DOES have a very good error detection mechanism (chunking and MD5 hashing the chunks). Yes, bittorrent does use UDP for transmission, but has its own error detection/correction/retransmit mechanism.</p></htmltext>
<tokenext>UDP is ( on its own ) not the solution , because when a UDP packet gets lost , there is n't a mechanism in the protocol to let the sender know to retransmit .
In this case , they are having packets received that are malformed/missing.The actual problem , here , is that FTP relies exclusively on TCP for error detection .
TCP 's error detection mechanism is extremely simple , and apparently too weak to resist the terrible transmission errors introduced on the second leg of the network.Now , if you 're not too worried about overhead , Bittorrent DOES have a very good error detection mechanism ( chunking and MD5 hashing the chunks ) .
Yes , bittorrent does use UDP for transmission , but has its own error detection/correction/retransmit mechanism .</tokentext>
<sentencetext>UDP is (on its own) not the solution, because when a UDP packet gets lost, there isn't a mechanism in the protocol to let the sender know to retransmit.
In this case, they are having packets received that are malformed/missing.The actual problem, here, is that FTP relies exclusively on TCP for error detection.
TCP's error detection mechanism is extremely simple, and apparently too weak to resist the terrible transmission errors introduced on the second leg of the network.Now, if you're not too worried about overhead, Bittorrent DOES have a very good error detection mechanism (chunking and MD5 hashing the chunks).
Yes, bittorrent does use UDP for transmission, but has its own error detection/correction/retransmit mechanism.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530395</id>
	<title>Re:TCP?</title>
	<author>mini me</author>
	<datestamp>1246383720000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>FTP, while in ASCII mode, can try to translate line endings. If the carriage returns were removed, in order to be UNIX compatible, the file size would have been reduced.</p><p>Most FTP clients allow the enabling of a binary mode which prevents the conversion from happening.</p></htmltext>
<tokenext>FTP , while in ASCII mode , can try to translate line endings .
If the carriage returns were removed , in order to be UNIX compatible , the file size would have been reduced.Most FTP clients allow the enabling of a binary mode which prevents the conversion from happening .</tokentext>
<sentencetext>FTP, while in ASCII mode, can try to translate line endings.
If the carriage returns were removed, in order to be UNIX compatible, the file size would have been reduced.Most FTP clients allow the enabling of a binary mode which prevents the conversion from happening.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530751</id>
	<title>Windows Server DFS</title>
	<author>Anonymous</author>
	<datestamp>1246384680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Also look into <a href="http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/default.mspx" title="microsoft.com" rel="nofollow">Windows</a> [microsoft.com] <a href="http://en.wikipedia.org/wiki/Distributed\_File\_System\_(Microsoft)" title="wikipedia.org" rel="nofollow">DFS</a> [wikipedia.org].</p><p>We use it to sync webfarm filesystems in Server 2008 and it works perfectly.  At least in 2008 only file changes are sent across so it is very efficient, even for WAN scenarios.</p><p>Best regards</p></htmltext>
<tokenext>Also look into Windows [ microsoft.com ] DFS [ wikipedia.org ] .We use it to sync webfarm filesystems in Server 2008 and it works perfectly .
At least in 2008 only file changes are sent across so it is very efficient , even for WAN scenarios.Best regards</tokentext>
<sentencetext>Also look into Windows [microsoft.com] DFS [wikipedia.org].We use it to sync webfarm filesystems in Server 2008 and it works perfectly.
At least in 2008 only file changes are sent across so it is very efficient, even for WAN scenarios.Best regards</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531985</id>
	<title>operator error</title>
	<author>Anonymous</author>
	<datestamp>1246388280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>&gt;<br>&gt; they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals<br>&gt;<br>This sound like operator error, probably transferring binary files in ASCII mode. TCP/IP already takes care of the reliable delivery.</p></htmltext>
<tokenext>&gt; &gt; they 've been using FTP to upload the files , but many times the copied files are a few kilobytes smaller than the originals &gt; This sound like operator error , probably transferring binary files in ASCII mode .
TCP/IP already takes care of the reliable delivery .</tokentext>
<sentencetext>&gt;&gt; they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals&gt;This sound like operator error, probably transferring binary files in ASCII mode.
TCP/IP already takes care of the reliable delivery.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532391</id>
	<title>FTP Losing Data?</title>
	<author>tignet</author>
	<datestamp>1246389720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>FTP rides over TCP so it isn't really possible to "lose" data. However the default FTP transfer mode for Windows is ASCII. This means that if you're transferring binary data that some might not make it through as expected.<br>
<br>
Change the FTP transfer mode to binary for the transfers and you won't have a problem. The command is "bin" once you have the FTP client open (assuming you're in interactive mode).</htmltext>
<tokenext>FTP rides over TCP so it is n't really possible to " lose " data .
However the default FTP transfer mode for Windows is ASCII .
This means that if you 're transferring binary data that some might not make it through as expected .
Change the FTP transfer mode to binary for the transfers and you wo n't have a problem .
The command is " bin " once you have the FTP client open ( assuming you 're in interactive mode ) .</tokentext>
<sentencetext>FTP rides over TCP so it isn't really possible to "lose" data.
However the default FTP transfer mode for Windows is ASCII.
This means that if you're transferring binary data that some might not make it through as expected.
Change the FTP transfer mode to binary for the transfers and you won't have a problem.
The command is "bin" once you have the FTP client open (assuming you're in interactive mode).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530525</id>
	<title>Re:TCP?</title>
	<author>theCoder</author>
	<datestamp>1246384020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's possible the files were transferred in ASCII mode.  This means that any place a '\r\n' appeared in the file, it was replaced by a '\n'.  This is normally OK (and sometimes desirable) for text files, but can really cause problems with binary files.  Because \r is 0x0d and \n is 0x0a, they can often appear in sequence in that in a binary file (like two pixels in an image) when they do not mean a line break.</p><p>I would recommend that the submitted check to make sure that binary mode was enabled in the FTP client and also to generate MD5 sums for the files before and after transit.  The MD5 sums will tell you if the file's contents were changed.</p></htmltext>
<tokenext>It 's possible the files were transferred in ASCII mode .
This means that any place a ' \ r \ n ' appeared in the file , it was replaced by a ' \ n' .
This is normally OK ( and sometimes desirable ) for text files , but can really cause problems with binary files .
Because \ r is 0x0d and \ n is 0x0a , they can often appear in sequence in that in a binary file ( like two pixels in an image ) when they do not mean a line break.I would recommend that the submitted check to make sure that binary mode was enabled in the FTP client and also to generate MD5 sums for the files before and after transit .
The MD5 sums will tell you if the file 's contents were changed .</tokentext>
<sentencetext>It's possible the files were transferred in ASCII mode.
This means that any place a '\r\n' appeared in the file, it was replaced by a '\n'.
This is normally OK (and sometimes desirable) for text files, but can really cause problems with binary files.
Because \r is 0x0d and \n is 0x0a, they can often appear in sequence in that in a binary file (like two pixels in an image) when they do not mean a line break.I would recommend that the submitted check to make sure that binary mode was enabled in the FTP client and also to generate MD5 sums for the files before and after transit.
The MD5 sums will tell you if the file's contents were changed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540469</id>
	<title>MQSeries</title>
	<author>Anonymous</author>
	<datestamp>1246450800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Or 'WebSphere MQ' for you young'uns.</p><p>http://en.wikipedia.org/wiki/IBM\_WebSphere\_MQ</p></htmltext>
<tokenext>Or 'WebSphere MQ ' for you young'uns.http : //en.wikipedia.org/wiki/IBM \ _WebSphere \ _MQ</tokentext>
<sentencetext>Or 'WebSphere MQ' for you young'uns.http://en.wikipedia.org/wiki/IBM\_WebSphere\_MQ</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531201</id>
	<title>Re:Any encrypted transmission protocol actually</title>
	<author>msimm</author>
	<datestamp>1246385760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I know people post publicly about using FTP for *ANYTHING* do it just to make me feel smarter but that summary included the words <i>mission critical</i>, <i>Windows</i> AND <i>FTP</i>.<br> <br>
*head explodes*</htmltext>
<tokenext>I know people post publicly about using FTP for * ANYTHING * do it just to make me feel smarter but that summary included the words mission critical , Windows AND FTP .
* head explodes *</tokentext>
<sentencetext>I know people post publicly about using FTP for *ANYTHING* do it just to make me feel smarter but that summary included the words mission critical, Windows AND FTP.
*head explodes*</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531043</id>
	<title>Re:Any encrypted transmission protocol actually</title>
	<author>Itninja</author>
	<datestamp>1246385280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Since there are several concepts/protocols that like to call themselves "SFTP", which one are you referring to?
<a href="http://en.wikipedia.org/wiki/Sftp" title="wikipedia.org">http://en.wikipedia.org/wiki/Sftp</a> [wikipedia.org]</htmltext>
<tokenext>Since there are several concepts/protocols that like to call themselves " SFTP " , which one are you referring to ?
http : //en.wikipedia.org/wiki/Sftp [ wikipedia.org ]</tokentext>
<sentencetext>Since there are several concepts/protocols that like to call themselves "SFTP", which one are you referring to?
http://en.wikipedia.org/wiki/Sftp [wikipedia.org]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530673</id>
	<title>Once-And-Only-Once</title>
	<author>Anonymous</author>
	<datestamp>1246384440000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Several posters have mentioned that TCP is a reliable transmission protocol, but it doesn't guarantee anything above the actual network layer.  If what you're looking for is guaranteed "once-and-only-once" transmission at the level of each message or file or whatever that you're transmitting, you need a transactional message queue -- something like "mqueue series."  These are basically network-transparent queues, where you can put something on the queue at one end of the network and pull it off the queue on the other end.  It's guaranteed to make it to the other side once and only once.  The protocols are built on TCP, but give you transactional guarantees at a higher level.</p></htmltext>
<tokenext>Several posters have mentioned that TCP is a reliable transmission protocol , but it does n't guarantee anything above the actual network layer .
If what you 're looking for is guaranteed " once-and-only-once " transmission at the level of each message or file or whatever that you 're transmitting , you need a transactional message queue -- something like " mqueue series .
" These are basically network-transparent queues , where you can put something on the queue at one end of the network and pull it off the queue on the other end .
It 's guaranteed to make it to the other side once and only once .
The protocols are built on TCP , but give you transactional guarantees at a higher level .</tokentext>
<sentencetext>Several posters have mentioned that TCP is a reliable transmission protocol, but it doesn't guarantee anything above the actual network layer.
If what you're looking for is guaranteed "once-and-only-once" transmission at the level of each message or file or whatever that you're transmitting, you need a transactional message queue -- something like "mqueue series.
"  These are basically network-transparent queues, where you can put something on the queue at one end of the network and pull it off the queue on the other end.
It's guaranteed to make it to the other side once and only once.
The protocols are built on TCP, but give you transactional guarantees at a higher level.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531239</id>
	<title>Re:TCP?</title>
	<author>bwcbwc</author>
	<datestamp>1246385880000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>I used to get dropped characters and groups of characters in text files using FTP back in the 1990s and early 21st century. It seemed to be a bug in the FTP client, because it only happened when we used the Windows Explorer interface for the product. When we did command line or used the native GUI there was no problem. If you're seeing this type of a pattern where you can see that characters are missing, switch to a different FTP client or try the Windows command line FTP.</p><p>Another possibility is that the target Windows system is mimicking a Unix system, so that an ASCII transfer is stripping the CR characters from CR/LF sequences.</p><p>On the other hand, if you really want a "guaranteed delivery" with formal acknowledgment and validation, try using a secured protocol like SSH or SFTP or a messaging system like JMS with a handshaking architecture around it. There are plenty of Open Source architectures you can build around (xBus for example), but I don't know of any ready-built executables. Commercially, vendors like IBM (MQ) and Tibco have products that deal with the messaging at a similar level.</p></htmltext>
<tokenext>I used to get dropped characters and groups of characters in text files using FTP back in the 1990s and early 21st century .
It seemed to be a bug in the FTP client , because it only happened when we used the Windows Explorer interface for the product .
When we did command line or used the native GUI there was no problem .
If you 're seeing this type of a pattern where you can see that characters are missing , switch to a different FTP client or try the Windows command line FTP.Another possibility is that the target Windows system is mimicking a Unix system , so that an ASCII transfer is stripping the CR characters from CR/LF sequences.On the other hand , if you really want a " guaranteed delivery " with formal acknowledgment and validation , try using a secured protocol like SSH or SFTP or a messaging system like JMS with a handshaking architecture around it .
There are plenty of Open Source architectures you can build around ( xBus for example ) , but I do n't know of any ready-built executables .
Commercially , vendors like IBM ( MQ ) and Tibco have products that deal with the messaging at a similar level .</tokentext>
<sentencetext>I used to get dropped characters and groups of characters in text files using FTP back in the 1990s and early 21st century.
It seemed to be a bug in the FTP client, because it only happened when we used the Windows Explorer interface for the product.
When we did command line or used the native GUI there was no problem.
If you're seeing this type of a pattern where you can see that characters are missing, switch to a different FTP client or try the Windows command line FTP.Another possibility is that the target Windows system is mimicking a Unix system, so that an ASCII transfer is stripping the CR characters from CR/LF sequences.On the other hand, if you really want a "guaranteed delivery" with formal acknowledgment and validation, try using a secured protocol like SSH or SFTP or a messaging system like JMS with a handshaking architecture around it.
There are plenty of Open Source architectures you can build around (xBus for example), but I don't know of any ready-built executables.
Commercially, vendors like IBM (MQ) and Tibco have products that deal with the messaging at a similar level.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530867</id>
	<title>Use .complete files.</title>
	<author>Prof.Phreak</author>
	<datestamp>1246384860000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>Even on reliable connections, using<nobr> <wbr></nobr>.complete files is a great idea.</p><p>It works this way: If you're pushing, open ftp, after ftp completes, you check remote filesize, if matches local file size, you also ftp a 0 size<nobr> <wbr></nobr>.complete file (or a $filename.complete file with md5 checksum, if you want to be extra paranoid).</p><p>Any app that reads that file will first check if<nobr> <wbr></nobr>.complete file is there.</p><p>If remote file size is less, you resume upload. If remove filesize is more than local, you wipe out remote file and restart.</p><p>Same idea for the reverse side (if you're pulling the file, instead of pushing).</p><p>You can also setup scripts to run every 5 minutes, and only stop retrying once<nobr> <wbr></nobr>.complete file is written (or read).</p><p>Note that the above would work even if the connection was interrupted and restarted a dozen times during the transmission. [we use this in $bigcorp to transfer hundreds of gigs of financial data per day... seems to work great; never had to care for maintenance windows, 'cause in the end, the file will get there anyway (scripts won't stop trying until data is there)].</p></htmltext>
<tokenext>Even on reliable connections , using .complete files is a great idea.It works this way : If you 're pushing , open ftp , after ftp completes , you check remote filesize , if matches local file size , you also ftp a 0 size .complete file ( or a $ filename.complete file with md5 checksum , if you want to be extra paranoid ) .Any app that reads that file will first check if .complete file is there.If remote file size is less , you resume upload .
If remove filesize is more than local , you wipe out remote file and restart.Same idea for the reverse side ( if you 're pulling the file , instead of pushing ) .You can also setup scripts to run every 5 minutes , and only stop retrying once .complete file is written ( or read ) .Note that the above would work even if the connection was interrupted and restarted a dozen times during the transmission .
[ we use this in $ bigcorp to transfer hundreds of gigs of financial data per day... seems to work great ; never had to care for maintenance windows , 'cause in the end , the file will get there anyway ( scripts wo n't stop trying until data is there ) ] .</tokentext>
<sentencetext>Even on reliable connections, using .complete files is a great idea.It works this way: If you're pushing, open ftp, after ftp completes, you check remote filesize, if matches local file size, you also ftp a 0 size .complete file (or a $filename.complete file with md5 checksum, if you want to be extra paranoid).Any app that reads that file will first check if .complete file is there.If remote file size is less, you resume upload.
If remove filesize is more than local, you wipe out remote file and restart.Same idea for the reverse side (if you're pulling the file, instead of pushing).You can also setup scripts to run every 5 minutes, and only stop retrying once .complete file is written (or read).Note that the above would work even if the connection was interrupted and restarted a dozen times during the transmission.
[we use this in $bigcorp to transfer hundreds of gigs of financial data per day... seems to work great; never had to care for maintenance windows, 'cause in the end, the file will get there anyway (scripts won't stop trying until data is there)].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539293</id>
	<title>try rsync instead</title>
	<author>Anonymous</author>
	<datestamp>1246391580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>over ssh tunnel, it is secure, etc...</p><p>over openvpn tunnel, it uses UDP</p><p>ftp is over complicated and prone to trouble.</p></htmltext>
<tokenext>over ssh tunnel , it is secure , etc...over openvpn tunnel , it uses UDPftp is over complicated and prone to trouble .</tokentext>
<sentencetext>over ssh tunnel, it is secure, etc...over openvpn tunnel, it uses UDPftp is over complicated and prone to trouble.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531441</id>
	<title>Database?</title>
	<author>Tablizer</author>
	<datestamp>1246386480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I had a similar issue once, and kicked around the idea of making it database-centric instead of file centric and use something like ODBC. Files are first "parsed" into a database format and un-parsed back into files at the other end. The downside is that it may not work well for open-ended documents, but is primarily designed for CSV-like (delimited) or fixed-column ascii data files. The plan's schema somewhat resembled:<br><tt><br>table: lines<br>-----<br>line\_ID<nobr> <wbr></nobr>// for internal processing<br>file\_Ref<nobr> <wbr></nobr>// foreign key<br>line\_sequence<nobr> <wbr></nobr>// sequence in file<br>line\_text<br>line\_check\_sum</tt></p><p><tt>table: files<br>------<br>file\_ID<nobr> <wbr></nobr>// or name<br>file\_check\_sum<br>line\_count<br></tt><br>After a transmission session, the missing lines can be known using the line count, sequence number, and check-sums. Check-sum is merely the sum of all ascii character ordinal values. The algorithm is roughly:<br><tt><br>
&nbsp; &nbsp; save(requestFileInfo());<br>
&nbsp; &nbsp; save(requestFileContent());<nobr> <wbr></nobr>// first transfer pass<br>
&nbsp; &nbsp; while (lineList = determineBadLines()) {<br>
&nbsp; &nbsp; &nbsp; &nbsp; for lineID = each in lineList {<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; statusMessage("retrieving line " . lineID);<br>
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; requestResendLine(lineID);<br>
&nbsp; &nbsp; &nbsp; &nbsp; }<br>
&nbsp; &nbsp; }<br>
&nbsp; &nbsp; statusMessage("done.");<br></tt><br>You may also need a file info check-sum(s) to make sure the file list is good. You can try it without a database, but it's hard to get "random access" to the problem lines without it.</p></htmltext>
<tokenext>I had a similar issue once , and kicked around the idea of making it database-centric instead of file centric and use something like ODBC .
Files are first " parsed " into a database format and un-parsed back into files at the other end .
The downside is that it may not work well for open-ended documents , but is primarily designed for CSV-like ( delimited ) or fixed-column ascii data files .
The plan 's schema somewhat resembled : table : lines-----line \ _ID // for internal processingfile \ _Ref // foreign keyline \ _sequence // sequence in fileline \ _textline \ _check \ _sumtable : files------file \ _ID // or namefile \ _check \ _sumline \ _countAfter a transmission session , the missing lines can be known using the line count , sequence number , and check-sums .
Check-sum is merely the sum of all ascii character ordinal values .
The algorithm is roughly :     save ( requestFileInfo ( ) ) ;     save ( requestFileContent ( ) ) ; // first transfer pass     while ( lineList = determineBadLines ( ) ) {         for lineID = each in lineList {             statusMessage ( " retrieving line " .
lineID ) ;             requestResendLine ( lineID ) ;         }     }     statusMessage ( " done .
" ) ; You may also need a file info check-sum ( s ) to make sure the file list is good .
You can try it without a database , but it 's hard to get " random access " to the problem lines without it .</tokentext>
<sentencetext>I had a similar issue once, and kicked around the idea of making it database-centric instead of file centric and use something like ODBC.
Files are first "parsed" into a database format and un-parsed back into files at the other end.
The downside is that it may not work well for open-ended documents, but is primarily designed for CSV-like (delimited) or fixed-column ascii data files.
The plan's schema somewhat resembled:table: lines-----line\_ID // for internal processingfile\_Ref // foreign keyline\_sequence // sequence in fileline\_textline\_check\_sumtable: files------file\_ID // or namefile\_check\_sumline\_countAfter a transmission session, the missing lines can be known using the line count, sequence number, and check-sums.
Check-sum is merely the sum of all ascii character ordinal values.
The algorithm is roughly:
    save(requestFileInfo());
    save(requestFileContent()); // first transfer pass
    while (lineList = determineBadLines()) {
        for lineID = each in lineList {
            statusMessage("retrieving line " .
lineID);
            requestResendLine(lineID);
        }
    }
    statusMessage("done.
");You may also need a file info check-sum(s) to make sure the file list is good.
You can try it without a database, but it's hard to get "random access" to the problem lines without it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533507</id>
	<title>Teracopy...</title>
	<author>keith\_nt4</author>
	<datestamp>1246394340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The poster didn't say anything about scripting but I have noticed that the pro version of <a href="http://www.codesector.com/teracopy.php" title="codesector.com" rel="nofollow">teracopy</a> [codesector.com] has a original/destination CRC value listed next to each file copied. I don't actually have the pro version and you'd have to get creative with script host (or whatever) to script it but this could very well fullfill your requirements.</p><p>Also, XCOPY has a "verify" flag...better than nothing I suppose...</p></htmltext>
<tokenext>The poster did n't say anything about scripting but I have noticed that the pro version of teracopy [ codesector.com ] has a original/destination CRC value listed next to each file copied .
I do n't actually have the pro version and you 'd have to get creative with script host ( or whatever ) to script it but this could very well fullfill your requirements.Also , XCOPY has a " verify " flag...better than nothing I suppose.. .</tokentext>
<sentencetext>The poster didn't say anything about scripting but I have noticed that the pro version of teracopy [codesector.com] has a original/destination CRC value listed next to each file copied.
I don't actually have the pro version and you'd have to get creative with script host (or whatever) to script it but this could very well fullfill your requirements.Also, XCOPY has a "verify" flag...better than nothing I suppose...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530697</id>
	<title>That is to be expected</title>
	<author>kseise</author>
	<datestamp>1246384500000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>Think of this transfer model like a car, the further it goes, the more bytes are burned up.  they just need to be added back in with a network filling station.  I would look to google for a government approved provider.</htmltext>
<tokenext>Think of this transfer model like a car , the further it goes , the more bytes are burned up .
they just need to be added back in with a network filling station .
I would look to google for a government approved provider .</tokentext>
<sentencetext>Think of this transfer model like a car, the further it goes, the more bytes are burned up.
they just need to be added back in with a network filling station.
I would look to google for a government approved provider.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531479</id>
	<title>OpenVPN or ssh</title>
	<author>toby</author>
	<datestamp>1246386540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Give you reliable connectionless (UDP) or connected (TCP) options respectively.</p></htmltext>
<tokenext>Give you reliable connectionless ( UDP ) or connected ( TCP ) options respectively .</tokentext>
<sentencetext>Give you reliable connectionless (UDP) or connected (TCP) options respectively.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540363</id>
	<title>Candle-who?</title>
	<author>tepples</author>
	<datestamp>1246449420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>TCP is so horrible. I wish HTTP used UDP by default so I wouldn't have the pro</p></div><p>Kidnapped by CJ too, I take it?</p></div>
	</htmltext>
<tokenext>TCP is so horrible .
I wish HTTP used UDP by default so I would n't have the proKidnapped by CJ too , I take it ?</tokentext>
<sentencetext>TCP is so horrible.
I wish HTTP used UDP by default so I wouldn't have the proKidnapped by CJ too, I take it?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531923</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532265</id>
	<title>Skynet</title>
	<author>n30na</author>
	<datestamp>1246389300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Just get a big cannon/artillery gun/icbm and fire tapes of data, or flash drives even.  Just stuff them into nerf balls.  It'll work great, like a sneakernet but with explosions.<nobr> <wbr></nobr>:D</htmltext>
<tokenext>Just get a big cannon/artillery gun/icbm and fire tapes of data , or flash drives even .
Just stuff them into nerf balls .
It 'll work great , like a sneakernet but with explosions .
: D</tokentext>
<sentencetext>Just get a big cannon/artillery gun/icbm and fire tapes of data, or flash drives even.
Just stuff them into nerf balls.
It'll work great, like a sneakernet but with explosions.
:D</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28537123</id>
	<title>If there's a budget, try this</title>
	<author>Anonymous</author>
	<datestamp>1246370040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You are looking for SkyPipe by AOS:  http://www.aosusa.com/products\_and\_technologies/skypipe.html  It works in exactly this scenario.</p></htmltext>
<tokenext>You are looking for SkyPipe by AOS : http : //www.aosusa.com/products \ _and \ _technologies/skypipe.html It works in exactly this scenario .</tokentext>
<sentencetext>You are looking for SkyPipe by AOS:  http://www.aosusa.com/products\_and\_technologies/skypipe.html  It works in exactly this scenario.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532785</id>
	<title>Are you sure about the difference in file size?</title>
	<author>Anonymous</author>
	<datestamp>1246391100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Different allocation unit sizes between disks can cause a file size to appear different across two machines...</p></htmltext>
<tokenext>Different allocation unit sizes between disks can cause a file size to appear different across two machines.. .</tokentext>
<sentencetext>Different allocation unit sizes between disks can cause a file size to appear different across two machines...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531465</id>
	<title>Snarky Response</title>
	<author>Anonymous</author>
	<datestamp>1246386540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Try using FedEX</htmltext>
<tokenext>Try using FedEX</tokentext>
<sentencetext>Try using FedEX</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532469</id>
	<title>Re:Guaranteed?</title>
	<author>gandhi\_2</author>
	<datestamp>1246389960000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>I worked on a system for the Utah DNR once. Data about sensitive species, species of concern, and endangered species have security requirements. If someone finds out how many Woundfin we are down to...the terrorist win.</htmltext>
<tokenext>I worked on a system for the Utah DNR once .
Data about sensitive species , species of concern , and endangered species have security requirements .
If someone finds out how many Woundfin we are down to...the terrorist win .</tokentext>
<sentencetext>I worked on a system for the Utah DNR once.
Data about sensitive species, species of concern, and endangered species have security requirements.
If someone finds out how many Woundfin we are down to...the terrorist win.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530943</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533679</id>
	<title>Putty, SFTP, CYGWIN</title>
	<author>Paracelcus</author>
	<datestamp>1246395000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I would think that you would want something more secure that FTP or windows copy, even rsync should be across a secure connection.</p></htmltext>
<tokenext>I would think that you would want something more secure that FTP or windows copy , even rsync should be across a secure connection .</tokentext>
<sentencetext>I would think that you would want something more secure that FTP or windows copy, even rsync should be across a secure connection.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28570353</id>
	<title>Cygwin w/ rsync over ssh</title>
	<author>goatbar</author>
	<datestamp>1246627140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Installing cygwin w/ cron, rsync and ssh is the only way to fly if you have to go by windows....
<p>
$ cygrunsrv -I cron -p<nobr> <wbr></nobr>/usr/sbin/cron -a -D<br>
$ net start cron
</p><p>
Or... install some linux distro and get the real thing</p></htmltext>
<tokenext>Installing cygwin w/ cron , rsync and ssh is the only way to fly if you have to go by windows... . $ cygrunsrv -I cron -p /usr/sbin/cron -a -D $ net start cron Or... install some linux distro and get the real thing</tokentext>
<sentencetext>Installing cygwin w/ cron, rsync and ssh is the only way to fly if you have to go by windows....

$ cygrunsrv -I cron -p /usr/sbin/cron -a -D
$ net start cron

Or... install some linux distro and get the real thing</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455</id>
	<title>RTFM - set binary mode in FTP</title>
	<author>n4djs</author>
	<datestamp>1246383900000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>
'set mode binary' prior to moving the file. I bet the file you are moving isn't a text file with CR-LF line terminations as normally found in DOS, or one side is set and the other isn't.
<p>
Ritchie's Law - assume you have screwed something up *first*, before blaming the tool...</p></htmltext>
<tokenext>'set mode binary ' prior to moving the file .
I bet the file you are moving is n't a text file with CR-LF line terminations as normally found in DOS , or one side is set and the other is n't .
Ritchie 's Law - assume you have screwed something up * first * , before blaming the tool.. .</tokentext>
<sentencetext>
'set mode binary' prior to moving the file.
I bet the file you are moving isn't a text file with CR-LF line terminations as normally found in DOS, or one side is set and the other isn't.
Ritchie's Law - assume you have screwed something up *first*, before blaming the tool...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532545</id>
	<title>Unison</title>
	<author>nightfire-unique</author>
	<datestamp>1246390200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Check out <a href="http://www.cis.upenn.edu/~bcpierce/unison/" title="upenn.edu">unison</a> [upenn.edu].</p><p>Directory synchronization over several protocols, brilliant include/exclude syntax, failure protection &amp; rollback, rsync style 1-way or 2-way block synchronization and intelligent file change detection, Unix and Windows support, open source...  It's what you need.</p></htmltext>
<tokenext>Check out unison [ upenn.edu ] .Directory synchronization over several protocols , brilliant include/exclude syntax , failure protection &amp; rollback , rsync style 1-way or 2-way block synchronization and intelligent file change detection , Unix and Windows support , open source... It 's what you need .</tokentext>
<sentencetext>Check out unison [upenn.edu].Directory synchronization over several protocols, brilliant include/exclude syntax, failure protection &amp; rollback, rsync style 1-way or 2-way block synchronization and intelligent file change detection, Unix and Windows support, open source...  It's what you need.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28546545</id>
	<title>FTP Support Nightmare</title>
	<author>Anonymous</author>
	<datestamp>1246476300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If you're just sending files to yourself, then you can probably choose FTP and still live a productive and meaningful life.</p><p>However, if you have users, I strongly recommend against using FTP.</p><p>I had to set up a FTP server so that some business partners could send us regular bulk updates.</p><p>Setting up the firewalls was a nightmare. Did you know that FTP uses 2 socket connections? One for command and another for data. I didn't. The ports used for the second data socket are arbitrary. I know almost nothing about TCP/IP, networks, etc. and had zero control over the network administration. Imagine trying to resolve firewall issues alongside other know-nothings.</p><p>The FTP protocol has evolved over time, making configuration a nightmare. Being a legacy protocol, the client and server aren't smart enough to negotiate the protocol settings. No, you have to tell the user exactly how to configure their client. Some fun. Most the users were domain experts, not even IT monkeys or devs. "It doesn't work" was about the extent of the feedback I'd get.</p><p>Eventually, I ended up surveying the FTP clients the customers were using, installing them all on my machine, figuring out how to get all those fuckers configured, documenting (with screen captures) all the settings, and hope the users followed my instructions exactly. This process took months.</p><p>Don't even think about using FTP+SSH. Every client and server handles those things differently. If use a self-signed certificate and the clients freak out with warnings, so then the users think they're being hacked. I used FileZilla, which wasn't horrible. But getting that fucker to use my certificate was a chore.</p><p>My recommendation is to use secure copy over SSH. Putty is a pretty simple, if butt ugly, client.</p></htmltext>
<tokenext>If you 're just sending files to yourself , then you can probably choose FTP and still live a productive and meaningful life.However , if you have users , I strongly recommend against using FTP.I had to set up a FTP server so that some business partners could send us regular bulk updates.Setting up the firewalls was a nightmare .
Did you know that FTP uses 2 socket connections ?
One for command and another for data .
I did n't .
The ports used for the second data socket are arbitrary .
I know almost nothing about TCP/IP , networks , etc .
and had zero control over the network administration .
Imagine trying to resolve firewall issues alongside other know-nothings.The FTP protocol has evolved over time , making configuration a nightmare .
Being a legacy protocol , the client and server are n't smart enough to negotiate the protocol settings .
No , you have to tell the user exactly how to configure their client .
Some fun .
Most the users were domain experts , not even IT monkeys or devs .
" It does n't work " was about the extent of the feedback I 'd get.Eventually , I ended up surveying the FTP clients the customers were using , installing them all on my machine , figuring out how to get all those fuckers configured , documenting ( with screen captures ) all the settings , and hope the users followed my instructions exactly .
This process took months.Do n't even think about using FTP + SSH .
Every client and server handles those things differently .
If use a self-signed certificate and the clients freak out with warnings , so then the users think they 're being hacked .
I used FileZilla , which was n't horrible .
But getting that fucker to use my certificate was a chore.My recommendation is to use secure copy over SSH .
Putty is a pretty simple , if butt ugly , client .</tokentext>
<sentencetext>If you're just sending files to yourself, then you can probably choose FTP and still live a productive and meaningful life.However, if you have users, I strongly recommend against using FTP.I had to set up a FTP server so that some business partners could send us regular bulk updates.Setting up the firewalls was a nightmare.
Did you know that FTP uses 2 socket connections?
One for command and another for data.
I didn't.
The ports used for the second data socket are arbitrary.
I know almost nothing about TCP/IP, networks, etc.
and had zero control over the network administration.
Imagine trying to resolve firewall issues alongside other know-nothings.The FTP protocol has evolved over time, making configuration a nightmare.
Being a legacy protocol, the client and server aren't smart enough to negotiate the protocol settings.
No, you have to tell the user exactly how to configure their client.
Some fun.
Most the users were domain experts, not even IT monkeys or devs.
"It doesn't work" was about the extent of the feedback I'd get.Eventually, I ended up surveying the FTP clients the customers were using, installing them all on my machine, figuring out how to get all those fuckers configured, documenting (with screen captures) all the settings, and hope the users followed my instructions exactly.
This process took months.Don't even think about using FTP+SSH.
Every client and server handles those things differently.
If use a self-signed certificate and the clients freak out with warnings, so then the users think they're being hacked.
I used FileZilla, which wasn't horrible.
But getting that fucker to use my certificate was a chore.My recommendation is to use secure copy over SSH.
Putty is a pretty simple, if butt ugly, client.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530623</id>
	<title>How about bittorrent?</title>
	<author>Anonymous</author>
	<datestamp>1246384320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It can even copy when the cableco sends spoofed FIN packets to reset connections.</p></htmltext>
<tokenext>It can even copy when the cableco sends spoofed FIN packets to reset connections .</tokentext>
<sentencetext>It can even copy when the cableco sends spoofed FIN packets to reset connections.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533129</id>
	<title>Assured UDP based file transfer systems</title>
	<author>TheSync</author>
	<datestamp>1246392600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Here are the UDP-based file transfer systems that I prefer:</p><p><a href="http://www.kencast.com/" title="kencast.com">Kencast</a> [kencast.com] has been the leader in multicast IP satellite file transfer (where all kinds of weird things can happen in Ku band), now they have a system called BlazeBand built for point-to-point IP connections that used their FAZZT Forward Error Correction technology, validation algorithm, and missed packet collector algorithms.   I've used FAZZT over satellite, but haven't tried BlazeBand yet.</p><p><a href="http://www.asperasoft.com/" title="asperasoft.com">Aspera</a> [asperasoft.com] is also widely used as a point-to-point UDP file transfer system in the entertainment industry.  I've seen it used to move large video files for network television programming.</p></htmltext>
<tokenext>Here are the UDP-based file transfer systems that I prefer : Kencast [ kencast.com ] has been the leader in multicast IP satellite file transfer ( where all kinds of weird things can happen in Ku band ) , now they have a system called BlazeBand built for point-to-point IP connections that used their FAZZT Forward Error Correction technology , validation algorithm , and missed packet collector algorithms .
I 've used FAZZT over satellite , but have n't tried BlazeBand yet.Aspera [ asperasoft.com ] is also widely used as a point-to-point UDP file transfer system in the entertainment industry .
I 've seen it used to move large video files for network television programming .</tokentext>
<sentencetext>Here are the UDP-based file transfer systems that I prefer:Kencast [kencast.com] has been the leader in multicast IP satellite file transfer (where all kinds of weird things can happen in Ku band), now they have a system called BlazeBand built for point-to-point IP connections that used their FAZZT Forward Error Correction technology, validation algorithm, and missed packet collector algorithms.
I've used FAZZT over satellite, but haven't tried BlazeBand yet.Aspera [asperasoft.com] is also widely used as a point-to-point UDP file transfer system in the entertainment industry.
I've seen it used to move large video files for network television programming.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539509</id>
	<title>What about Rysnc?</title>
	<author>Golthar</author>
	<datestamp>1246481100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><a href="http://www.samba.org/rsync/" title="samba.org">http://www.samba.org/rsync/</a> [samba.org]</p><p>Or something like it in Windows.<br>It will check the delivered files, retry chunks if needed.<br>Much better than just FTP</p></htmltext>
<tokenext>http : //www.samba.org/rsync/ [ samba.org ] Or something like it in Windows.It will check the delivered files , retry chunks if needed.Much better than just FTP</tokentext>
<sentencetext>http://www.samba.org/rsync/ [samba.org]Or something like it in Windows.It will check the delivered files, retry chunks if needed.Much better than just FTP</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535035</id>
	<title>Re:TCP?</title>
	<author>jeremyp</author>
	<datestamp>1246357680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This is bullshit.</p><p>No real file system in the world does not know the the exact size of a file to the byte.  Otherwise almost every file you open would have whatever garbage at the end of it that was in the last block.</p><p>Certainly Windows and Unix will always report file sizes to the byte.</p></htmltext>
<tokenext>This is bullshit.No real file system in the world does not know the the exact size of a file to the byte .
Otherwise almost every file you open would have whatever garbage at the end of it that was in the last block.Certainly Windows and Unix will always report file sizes to the byte .</tokentext>
<sentencetext>This is bullshit.No real file system in the world does not know the the exact size of a file to the byte.
Otherwise almost every file you open would have whatever garbage at the end of it that was in the last block.Certainly Windows and Unix will always report file sizes to the byte.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530437</id>
	<title>Confirm the data loss first</title>
	<author>Sockatume</author>
	<datestamp>1246383840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Take an MD5 hash of the data or something, then send it. If it comes back changed, you've got data loss. If it comes back the same, and the files are still a few kb smaller, then either you're the Wizard of File Hashes or you're reading off on-disk size instead of actual data size.</p></htmltext>
<tokenext>Take an MD5 hash of the data or something , then send it .
If it comes back changed , you 've got data loss .
If it comes back the same , and the files are still a few kb smaller , then either you 're the Wizard of File Hashes or you 're reading off on-disk size instead of actual data size .</tokentext>
<sentencetext>Take an MD5 hash of the data or something, then send it.
If it comes back changed, you've got data loss.
If it comes back the same, and the files are still a few kb smaller, then either you're the Wizard of File Hashes or you're reading off on-disk size instead of actual data size.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531321</id>
	<title>Re:Correct me if I'm wrong...</title>
	<author>canuck08</author>
	<datestamp>1246386120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>he's not really looking for a protocol.  He needs an app.<br>99.99999\% chance whatever app he decides to use will be using TCP.</p></htmltext>
<tokenext>he 's not really looking for a protocol .
He needs an app.99.99999 \ % chance whatever app he decides to use will be using TCP .</tokentext>
<sentencetext>he's not really looking for a protocol.
He needs an app.99.99999\% chance whatever app he decides to use will be using TCP.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540641</id>
	<title>Re:UDP.</title>
	<author>Phreakiture</author>
	<datestamp>1246452900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Okay, getting serious now . .<nobr> <wbr></nobr>.</p><p>First, it sounds like a file size difference of a few kilobytes could be attributed to ASCII vs. binary mode in FTP</p><p>Second, if, after checking that, you do decide to retire FTP, I'd suggest using http, if, and only if, you can initiate the file transfer from the receiving end.  Use wget with the --tries=&lt;big\_number&gt; and --continue flags.</p><p>Another option is to chunk the data.  You may have to brew something yourself here, but if you can chunk the data and then validate the chunks by a hashing algorithm (MD5, SHA, etc), you can re-request the b0rked chunks before attempting to re-assemble the file.</p><p>On UDP . . . While I don't necessarily advocate TIBCO per se, they do have a UDP-based system (Rendezvous) that has an option that they call a "certified" delivery -- missed packets can be re-requested.  It's really more intended for one-to-many transmissions, but it (or a competitor) might be an option.</p></htmltext>
<tokenext>Okay , getting serious now .
. .First , it sounds like a file size difference of a few kilobytes could be attributed to ASCII vs. binary mode in FTPSecond , if , after checking that , you do decide to retire FTP , I 'd suggest using http , if , and only if , you can initiate the file transfer from the receiving end .
Use wget with the --tries = and --continue flags.Another option is to chunk the data .
You may have to brew something yourself here , but if you can chunk the data and then validate the chunks by a hashing algorithm ( MD5 , SHA , etc ) , you can re-request the b0rked chunks before attempting to re-assemble the file.On UDP .
. .
While I do n't necessarily advocate TIBCO per se , they do have a UDP-based system ( Rendezvous ) that has an option that they call a " certified " delivery -- missed packets can be re-requested .
It 's really more intended for one-to-many transmissions , but it ( or a competitor ) might be an option .</tokentext>
<sentencetext>Okay, getting serious now .
. .First, it sounds like a file size difference of a few kilobytes could be attributed to ASCII vs. binary mode in FTPSecond, if, after checking that, you do decide to retire FTP, I'd suggest using http, if, and only if, you can initiate the file transfer from the receiving end.
Use wget with the --tries= and --continue flags.Another option is to chunk the data.
You may have to brew something yourself here, but if you can chunk the data and then validate the chunks by a hashing algorithm (MD5, SHA, etc), you can re-request the b0rked chunks before attempting to re-assemble the file.On UDP .
. .
While I don't necessarily advocate TIBCO per se, they do have a UDP-based system (Rendezvous) that has an option that they call a "certified" delivery -- missed packets can be re-requested.
It's really more intended for one-to-many transmissions, but it (or a competitor) might be an option.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530279</id>
	<title>BitTorrent</title>
	<author>russotto</author>
	<datestamp>1246383420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's crazy but it just might work.  Not very quickly though.</htmltext>
<tokenext>It 's crazy but it just might work .
Not very quickly though .</tokentext>
<sentencetext>It's crazy but it just might work.
Not very quickly though.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531561</id>
	<title>Doubletake</title>
	<author>emocomputerjock</author>
	<datestamp>1246386840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I know I'm late on this, but I haven't seen it mentioned yet. Doubletake is fantastic, and I've yet to have it fail me when moving stuff from point a to b on Windows systems. You didn't mention cost as a factor in the summary but I should note that it is most certainly not free, but if you have to make sure it gets there it may be worth it.</htmltext>
<tokenext>I know I 'm late on this , but I have n't seen it mentioned yet .
Doubletake is fantastic , and I 've yet to have it fail me when moving stuff from point a to b on Windows systems .
You did n't mention cost as a factor in the summary but I should note that it is most certainly not free , but if you have to make sure it gets there it may be worth it .</tokentext>
<sentencetext>I know I'm late on this, but I haven't seen it mentioned yet.
Doubletake is fantastic, and I've yet to have it fail me when moving stuff from point a to b on Windows systems.
You didn't mention cost as a factor in the summary but I should note that it is most certainly not free, but if you have to make sure it gets there it may be worth it.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531083</id>
	<title>Re:Two words:</title>
	<author>Culture20</author>
	<datestamp>1246385400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>RTFS.  They're transferring Microwaves!  Stick the DVDs in the Microwaves and let them get delivered by the normal delivery guy.  No need to fedEx.  Just don't turn the Microwaves on while the DVDs are still inside.</htmltext>
<tokenext>RTFS .
They 're transferring Microwaves !
Stick the DVDs in the Microwaves and let them get delivered by the normal delivery guy .
No need to fedEx .
Just do n't turn the Microwaves on while the DVDs are still inside .</tokentext>
<sentencetext>RTFS.
They're transferring Microwaves!
Stick the DVDs in the Microwaves and let them get delivered by the normal delivery guy.
No need to fedEx.
Just don't turn the Microwaves on while the DVDs are still inside.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530595</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</id>
	<title>You're kidding, aren't you??</title>
	<author>Anonymous</author>
	<datestamp>1246385520000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>You are kidding about this, aren't you?</p><p>Let me get the facts straight:</p><p>- you have "mission critical files", and the network you're transferring them over is so incredibly badly managed that it doesn't support reliable data transfer<br>- you want a technical workaround for this brokenness.</p><p>If this is the case, you don't have a technical problem on your hands; you have a political one.</p><p>"Mission critical" has a meaning: it means critical to the success of the operation.  I.e. without these files, your operation or someone else's operation will fail.</p><p>If your management believes that your files are "mission critical", and you're facing a problem of this sort, you need to document the difficulties you're having, along with measurements to support your claims and then make a clear statement that as long as your network path is completely broken, you are absolving yourself of responsiblility for the correct transmission of these files.</p><p>If your management doesn't do anything about this, then the files are not "mission critical".</p></htmltext>
<tokenext>You are kidding about this , are n't you ? Let me get the facts straight : - you have " mission critical files " , and the network you 're transferring them over is so incredibly badly managed that it does n't support reliable data transfer- you want a technical workaround for this brokenness.If this is the case , you do n't have a technical problem on your hands ; you have a political one .
" Mission critical " has a meaning : it means critical to the success of the operation .
I.e. without these files , your operation or someone else 's operation will fail.If your management believes that your files are " mission critical " , and you 're facing a problem of this sort , you need to document the difficulties you 're having , along with measurements to support your claims and then make a clear statement that as long as your network path is completely broken , you are absolving yourself of responsiblility for the correct transmission of these files.If your management does n't do anything about this , then the files are not " mission critical " .</tokentext>
<sentencetext>You are kidding about this, aren't you?Let me get the facts straight:- you have "mission critical files", and the network you're transferring them over is so incredibly badly managed that it doesn't support reliable data transfer- you want a technical workaround for this brokenness.If this is the case, you don't have a technical problem on your hands; you have a political one.
"Mission critical" has a meaning: it means critical to the success of the operation.
I.e. without these files, your operation or someone else's operation will fail.If your management believes that your files are "mission critical", and you're facing a problem of this sort, you need to document the difficulties you're having, along with measurements to support your claims and then make a clear statement that as long as your network path is completely broken, you are absolving yourself of responsiblility for the correct transmission of these files.If your management doesn't do anything about this, then the files are not "mission critical".</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532977</id>
	<title>Disguise as pr0n</title>
	<author>Anonymous</author>
	<datestamp>1246391880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Rename it hot\_chick.avi and it'll be there in no time. And since it's Windows, you could just make it a payload of some malware and let it spread there naturally.</htmltext>
<tokenext>Rename it hot \ _chick.avi and it 'll be there in no time .
And since it 's Windows , you could just make it a payload of some malware and let it spread there naturally .</tokentext>
<sentencetext>Rename it hot\_chick.avi and it'll be there in no time.
And since it's Windows, you could just make it a payload of some malware and let it spread there naturally.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531571</id>
	<title>Re:TCP?</title>
	<author>RasputinAXP</author>
	<datestamp>1246386900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Where are my mod points today?? a virtual +1, insightful to you</p></htmltext>
<tokenext>Where are my mod points today ? ?
a virtual + 1 , insightful to you</tokentext>
<sentencetext>Where are my mod points today??
a virtual +1, insightful to you</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542603</id>
	<title>Yeah, whatever..</title>
	<author>jotaeleemeese</author>
	<datestamp>1246464300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What do you suggest? That he introduces  optical fiber to the middle of Nowhereville?</p><p>Some times you have to deal with less than ideal situations for your job, yo will certainly have to explain that you'll find constraints, and yes, sometimes you may have to say that something is not possible, but mission critical does not mean what you think it does....</p></htmltext>
<tokenext>What do you suggest ?
That he introduces optical fiber to the middle of Nowhereville ? Some times you have to deal with less than ideal situations for your job , yo will certainly have to explain that you 'll find constraints , and yes , sometimes you may have to say that something is not possible , but mission critical does not mean what you think it does... .</tokentext>
<sentencetext>What do you suggest?
That he introduces  optical fiber to the middle of Nowhereville?Some times you have to deal with less than ideal situations for your job, yo will certainly have to explain that you'll find constraints, and yes, sometimes you may have to say that something is not possible, but mission critical does not mean what you think it does....</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121</id>
	<title>Re:TCP?</title>
	<author>Obfuscant</author>
	<datestamp>1246388760000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><i>Since ASCII files are also ultimately represented as particular sequences of binary data, why does FTP even have an ASCII transfer mode?</i> <p>
Because of differences between systems like Unix and Windows, where line ends are a simple newline on Unix but a CR/LF pair on Windows. Also systems like VMS which have (had) about thirteen different file formats all inherent in the file structure itself.</p><p>
In other words, because all ASCII files are not represented the same way by all different operating systems.</p><p>
<i>I know that Windows uses CR/LF for line termination and *nix uses just LF. That's a very minor inconvenience at worst,</i> </p><p>
Not if you have an "ASCII" file you are trying to read on Windows that has Unix newline conventions. Try opening a newlined file with notepad, for example.</p><p><nobr> <wbr></nobr><i>...and little standalone utilities to convert the formats are readily available and have been for some time now.</i> </p><p>
"Little standalone utilities" are really handy for small files and small numbers of files. It's really handy when you know the format the file you have is in and what it needs to be. Please tell me how you will identify a VMS fixed record file that you have just ftp'd from a VMS FTP server when it gets to your Windows system. It has NO newlines or CR/LF pairs. You might dump the file somehow and notice that the lines are all 93 characters long and then write yourself a perl script to split it up -- or you could simply tell your FTP client that you are in ASCII mode and let the FTP server/client negotiate some resulting format that your system likes. Now try that with a VMS variable length record file, where the lines are variable length, still without line endings.</p><p>
FTP wasn't designed just for hobbyists who want a file or two and have the time to deal with file formats by hand. It was designed to move data, and anything that can be automated should be. "Little standalone utilities" are a pain in the ass when trying to automate something, especially when the critical information necessary to know what specific utility to use has been lost, or is completely unknown to the recipient's system. Like VMS fixed length records on Unix or Windows.</p><p>
<i>It just seems like it's not the job of a file transfer protocol to concern itself with what an independent, unrelated application can or cannot do with the file after it's transferred.</i> </p><p>
ASCII mode in FTP has nothing to do with anyone trying to tell anyone what they can or cannot do with a file after it's transferred. It's all about knowing how to deal with a hundred different ways of representing ASCII data on dozens of different operating systems and making life EASIER for people who have to do that on a daily basis.</p><p>
If YOU would rather operate in BIN mode and worry about which file formats you've just downloaded and how to convert them to an ASCII representation that your software knows how to deal with, more power to you. I got tired of dealing with this the first time I had to convert a VMS "ASCII" file to Unix and I'll let FTP do it silently for me. Yes, I've dealt with users who didn't know what ASCII mode was and downloaded a zipped file in ASCII mode and it didn't work, but the time I've saved just myself not having to deal with converting crap has more than made up for the time I've spent telling them to use BIN mode.</p></htmltext>
<tokenext>Since ASCII files are also ultimately represented as particular sequences of binary data , why does FTP even have an ASCII transfer mode ?
Because of differences between systems like Unix and Windows , where line ends are a simple newline on Unix but a CR/LF pair on Windows .
Also systems like VMS which have ( had ) about thirteen different file formats all inherent in the file structure itself .
In other words , because all ASCII files are not represented the same way by all different operating systems .
I know that Windows uses CR/LF for line termination and * nix uses just LF .
That 's a very minor inconvenience at worst , Not if you have an " ASCII " file you are trying to read on Windows that has Unix newline conventions .
Try opening a newlined file with notepad , for example .
...and little standalone utilities to convert the formats are readily available and have been for some time now .
" Little standalone utilities " are really handy for small files and small numbers of files .
It 's really handy when you know the format the file you have is in and what it needs to be .
Please tell me how you will identify a VMS fixed record file that you have just ftp 'd from a VMS FTP server when it gets to your Windows system .
It has NO newlines or CR/LF pairs .
You might dump the file somehow and notice that the lines are all 93 characters long and then write yourself a perl script to split it up -- or you could simply tell your FTP client that you are in ASCII mode and let the FTP server/client negotiate some resulting format that your system likes .
Now try that with a VMS variable length record file , where the lines are variable length , still without line endings .
FTP was n't designed just for hobbyists who want a file or two and have the time to deal with file formats by hand .
It was designed to move data , and anything that can be automated should be .
" Little standalone utilities " are a pain in the ass when trying to automate something , especially when the critical information necessary to know what specific utility to use has been lost , or is completely unknown to the recipient 's system .
Like VMS fixed length records on Unix or Windows .
It just seems like it 's not the job of a file transfer protocol to concern itself with what an independent , unrelated application can or can not do with the file after it 's transferred .
ASCII mode in FTP has nothing to do with anyone trying to tell anyone what they can or can not do with a file after it 's transferred .
It 's all about knowing how to deal with a hundred different ways of representing ASCII data on dozens of different operating systems and making life EASIER for people who have to do that on a daily basis .
If YOU would rather operate in BIN mode and worry about which file formats you 've just downloaded and how to convert them to an ASCII representation that your software knows how to deal with , more power to you .
I got tired of dealing with this the first time I had to convert a VMS " ASCII " file to Unix and I 'll let FTP do it silently for me .
Yes , I 've dealt with users who did n't know what ASCII mode was and downloaded a zipped file in ASCII mode and it did n't work , but the time I 've saved just myself not having to deal with converting crap has more than made up for the time I 've spent telling them to use BIN mode .</tokentext>
<sentencetext>Since ASCII files are also ultimately represented as particular sequences of binary data, why does FTP even have an ASCII transfer mode?
Because of differences between systems like Unix and Windows, where line ends are a simple newline on Unix but a CR/LF pair on Windows.
Also systems like VMS which have (had) about thirteen different file formats all inherent in the file structure itself.
In other words, because all ASCII files are not represented the same way by all different operating systems.
I know that Windows uses CR/LF for line termination and *nix uses just LF.
That's a very minor inconvenience at worst, 
Not if you have an "ASCII" file you are trying to read on Windows that has Unix newline conventions.
Try opening a newlined file with notepad, for example.
...and little standalone utilities to convert the formats are readily available and have been for some time now.
"Little standalone utilities" are really handy for small files and small numbers of files.
It's really handy when you know the format the file you have is in and what it needs to be.
Please tell me how you will identify a VMS fixed record file that you have just ftp'd from a VMS FTP server when it gets to your Windows system.
It has NO newlines or CR/LF pairs.
You might dump the file somehow and notice that the lines are all 93 characters long and then write yourself a perl script to split it up -- or you could simply tell your FTP client that you are in ASCII mode and let the FTP server/client negotiate some resulting format that your system likes.
Now try that with a VMS variable length record file, where the lines are variable length, still without line endings.
FTP wasn't designed just for hobbyists who want a file or two and have the time to deal with file formats by hand.
It was designed to move data, and anything that can be automated should be.
"Little standalone utilities" are a pain in the ass when trying to automate something, especially when the critical information necessary to know what specific utility to use has been lost, or is completely unknown to the recipient's system.
Like VMS fixed length records on Unix or Windows.
It just seems like it's not the job of a file transfer protocol to concern itself with what an independent, unrelated application can or cannot do with the file after it's transferred.
ASCII mode in FTP has nothing to do with anyone trying to tell anyone what they can or cannot do with a file after it's transferred.
It's all about knowing how to deal with a hundred different ways of representing ASCII data on dozens of different operating systems and making life EASIER for people who have to do that on a daily basis.
If YOU would rather operate in BIN mode and worry about which file formats you've just downloaded and how to convert them to an ASCII representation that your software knows how to deal with, more power to you.
I got tired of dealing with this the first time I had to convert a VMS "ASCII" file to Unix and I'll let FTP do it silently for me.
Yes, I've dealt with users who didn't know what ASCII mode was and downloaded a zipped file in ASCII mode and it didn't work, but the time I've saved just myself not having to deal with converting crap has more than made up for the time I've spent telling them to use BIN mode.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533137</id>
	<title>Re:UDP.</title>
	<author>Chees0rz</author>
	<datestamp>1246392600000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>OYu need tdownoadl hte fxofire lugin</htmltext>
<tokenext>OYu need tdownoadl hte fxofire lugin</tokentext>
<sentencetext>OYu need tdownoadl hte fxofire lugin</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531923</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531039</id>
	<title>Bittorrent</title>
	<author>Aceticon</author>
	<datestamp>1246385280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I would reckon that something based on the Bittorrent protocol (or a subset of it) might be an exceptionally reliable way of, while running in the background, sending files from one machine to another one.</p><p>The protocol comes with built-in file splitting/recombination, block validation and you can get several GUIs (and I believe at least one command line implementation) for it. It might be a bit overkill though - pretty much everything in the protocol related to dealing with managing communications with multiple peers (most of the protocol really) is unlikely to be useful in your situation.</p><p>That said, your own private tracker listing one and only one peer all the time (the machine where the files are being read from) might be the only tricky bit you need to do to use any bittorrent implementation out there.</p></htmltext>
<tokenext>I would reckon that something based on the Bittorrent protocol ( or a subset of it ) might be an exceptionally reliable way of , while running in the background , sending files from one machine to another one.The protocol comes with built-in file splitting/recombination , block validation and you can get several GUIs ( and I believe at least one command line implementation ) for it .
It might be a bit overkill though - pretty much everything in the protocol related to dealing with managing communications with multiple peers ( most of the protocol really ) is unlikely to be useful in your situation.That said , your own private tracker listing one and only one peer all the time ( the machine where the files are being read from ) might be the only tricky bit you need to do to use any bittorrent implementation out there .</tokentext>
<sentencetext>I would reckon that something based on the Bittorrent protocol (or a subset of it) might be an exceptionally reliable way of, while running in the background, sending files from one machine to another one.The protocol comes with built-in file splitting/recombination, block validation and you can get several GUIs (and I believe at least one command line implementation) for it.
It might be a bit overkill though - pretty much everything in the protocol related to dealing with managing communications with multiple peers (most of the protocol really) is unlikely to be useful in your situation.That said, your own private tracker listing one and only one peer all the time (the machine where the files are being read from) might be the only tricky bit you need to do to use any bittorrent implementation out there.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539667</id>
	<title>Message Queuing</title>
	<author>Anonymous</author>
	<datestamp>1246439820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>There is an entire class of software out there called "Message Queueing" systems.<br>MQ systems have guaranteed delivery of your message once and only once over any network conditions.<br>There are several big name vendors that supply this stuff.<br>They usually cost around $5K per copy (please check pricing on your own).<br>They run on virtually all operating systems and platforms.</p><p>They work great!</p><p>All the other suggestions you got are crap.<br>FTP? Please guys...give me a break.</p><p>Mike M</p></htmltext>
<tokenext>There is an entire class of software out there called " Message Queueing " systems.MQ systems have guaranteed delivery of your message once and only once over any network conditions.There are several big name vendors that supply this stuff.They usually cost around $ 5K per copy ( please check pricing on your own ) .They run on virtually all operating systems and platforms.They work great ! All the other suggestions you got are crap.FTP ?
Please guys...give me a break.Mike M</tokentext>
<sentencetext>There is an entire class of software out there called "Message Queueing" systems.MQ systems have guaranteed delivery of your message once and only once over any network conditions.There are several big name vendors that supply this stuff.They usually cost around $5K per copy (please check pricing on your own).They run on virtually all operating systems and platforms.They work great!All the other suggestions you got are crap.FTP?
Please guys...give me a break.Mike M</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530589</id>
	<title>wget</title>
	<author>Anonymous</author>
	<datestamp>1246384260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It's not just for *nix any more.</p></htmltext>
<tokenext>It 's not just for * nix any more .</tokentext>
<sentencetext>It's not just for *nix any more.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530219</id>
	<title>ISCSI Mounted Partition on the remote...</title>
	<author>bagboy</author>
	<datestamp>1246383300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Should work fine across a WAN and then just file-copy.</htmltext>
<tokenext>Should work fine across a WAN and then just file-copy .</tokentext>
<sentencetext>Should work fine across a WAN and then just file-copy.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28566369</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246539420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Considering that both sides are windows, I'd say the chances of that are rather slim. Windows shows both normal size and "on disk" size.</p></htmltext>
<tokenext>Considering that both sides are windows , I 'd say the chances of that are rather slim .
Windows shows both normal size and " on disk " size .</tokentext>
<sentencetext>Considering that both sides are windows, I'd say the chances of that are rather slim.
Windows shows both normal size and "on disk" size.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531207</id>
	<title>Re:BitTorrent</title>
	<author>Anonymous</author>
	<datestamp>1246385820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Why wouldn't Bittorrent work as quickly? It is only limited by the upload speed. If 1 seed seeds to 1 peer, then the peer will download as fast as the seed can upload.</p></htmltext>
<tokenext>Why would n't Bittorrent work as quickly ?
It is only limited by the upload speed .
If 1 seed seeds to 1 peer , then the peer will download as fast as the seed can upload .</tokentext>
<sentencetext>Why wouldn't Bittorrent work as quickly?
It is only limited by the upload speed.
If 1 seed seeds to 1 peer, then the peer will download as fast as the seed can upload.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530279</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531049</id>
	<title>robocopy</title>
	<author>Anonymous</author>
	<datestamp>1246385340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Command line robocopy available from the various Windows administration kits for free.<br>It can run on a schedule or via the task scheduler or only when X amount of changes have been made, you can set interpacket gaps to limit speed, it logs transfers, it has switches for retries and wait times, it restarts and different methods for opening locked files, you can maintain NTFS file permissions or not, it can mirror, delete in destination.  It is a single exe file with nothing to install.  It can bescripted, run manually, or in a batch file with options.</p><p>Simple, easy, and it works.</p><p><a href="http://en.wikipedia.org/wiki/Robocopy" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Robocopy</a> [wikipedia.org]</p></htmltext>
<tokenext>Command line robocopy available from the various Windows administration kits for free.It can run on a schedule or via the task scheduler or only when X amount of changes have been made , you can set interpacket gaps to limit speed , it logs transfers , it has switches for retries and wait times , it restarts and different methods for opening locked files , you can maintain NTFS file permissions or not , it can mirror , delete in destination .
It is a single exe file with nothing to install .
It can bescripted , run manually , or in a batch file with options.Simple , easy , and it works.http : //en.wikipedia.org/wiki/Robocopy [ wikipedia.org ]</tokentext>
<sentencetext>Command line robocopy available from the various Windows administration kits for free.It can run on a schedule or via the task scheduler or only when X amount of changes have been made, you can set interpacket gaps to limit speed, it logs transfers, it has switches for retries and wait times, it restarts and different methods for opening locked files, you can maintain NTFS file permissions or not, it can mirror, delete in destination.
It is a single exe file with nothing to install.
It can bescripted, run manually, or in a batch file with options.Simple, easy, and it works.http://en.wikipedia.org/wiki/Robocopy [wikipedia.org]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532169</id>
	<title>Re:BitTorrent</title>
	<author>Anonymous</author>
	<datestamp>1246388880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Why would it be any slower than FTP? The data has to be transferred regardless of transport.</p><p>Of course you would want to encrypt the file. Maybe you will want to run your own tracker.</p><p>The only thing you will have to enable network-wise is one (or both) machines being able to establish a TCP connection to the other.</p><p>BitTorrent will then transfer the file and check its integrity at the receiving end.</p></htmltext>
<tokenext>Why would it be any slower than FTP ?
The data has to be transferred regardless of transport.Of course you would want to encrypt the file .
Maybe you will want to run your own tracker.The only thing you will have to enable network-wise is one ( or both ) machines being able to establish a TCP connection to the other.BitTorrent will then transfer the file and check its integrity at the receiving end .</tokentext>
<sentencetext>Why would it be any slower than FTP?
The data has to be transferred regardless of transport.Of course you would want to encrypt the file.
Maybe you will want to run your own tracker.The only thing you will have to enable network-wise is one (or both) machines being able to establish a TCP connection to the other.BitTorrent will then transfer the file and check its integrity at the receiving end.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530279</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531719</id>
	<title>Bah, Newsgroups.</title>
	<author>0100010001010011</author>
	<datestamp>1246387380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Take a note from the newsgroup file sharers. If it's good enough to share GB+ data on an old school discussion forum, it's good enough for your business.</p><p>1) Split the file into tiny rars, 1-10MB in size.<br>2) PAR2 the files with a decent amount of redundancy.<br>3) Send. Resume any broken files<br>4) Fix.</p><p>If you really wanted to get fancy. Run a news server on each end of the line. Upload files locally to the newsgroup and then grab them from the other end. The pirate community has a ton of tools for making this as painless as possible. (I heart hellanzb)</p></htmltext>
<tokenext>Take a note from the newsgroup file sharers .
If it 's good enough to share GB + data on an old school discussion forum , it 's good enough for your business.1 ) Split the file into tiny rars , 1-10MB in size.2 ) PAR2 the files with a decent amount of redundancy.3 ) Send .
Resume any broken files4 ) Fix.If you really wanted to get fancy .
Run a news server on each end of the line .
Upload files locally to the newsgroup and then grab them from the other end .
The pirate community has a ton of tools for making this as painless as possible .
( I heart hellanzb )</tokentext>
<sentencetext>Take a note from the newsgroup file sharers.
If it's good enough to share GB+ data on an old school discussion forum, it's good enough for your business.1) Split the file into tiny rars, 1-10MB in size.2) PAR2 the files with a decent amount of redundancy.3) Send.
Resume any broken files4) Fix.If you really wanted to get fancy.
Run a news server on each end of the line.
Upload files locally to the newsgroup and then grab them from the other end.
The pirate community has a ton of tools for making this as painless as possible.
(I heart hellanzb)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530279</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530997</id>
	<title>linux proxy</title>
	<author>The Cisco Kid</author>
	<datestamp>1246385220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Setup a linux box on the same network next to the windows box that is at the 'remote' end of the transfer (eg, not the end the transfer is initiated from).</p><p>Use ssh from the 'local' end to transfer the file to the linux box. Then run something appropriate (ftpd? apache? samba?) on the linux box that makes the files directly available to the windows box.</p><p>Alternatively, rip the Windows crap out and replace both ends with a real OS.</p></htmltext>
<tokenext>Setup a linux box on the same network next to the windows box that is at the 'remote ' end of the transfer ( eg , not the end the transfer is initiated from ) .Use ssh from the 'local ' end to transfer the file to the linux box .
Then run something appropriate ( ftpd ?
apache ? samba ?
) on the linux box that makes the files directly available to the windows box.Alternatively , rip the Windows crap out and replace both ends with a real OS .</tokentext>
<sentencetext>Setup a linux box on the same network next to the windows box that is at the 'remote' end of the transfer (eg, not the end the transfer is initiated from).Use ssh from the 'local' end to transfer the file to the linux box.
Then run something appropriate (ftpd?
apache? samba?
) on the linux box that makes the files directly available to the windows box.Alternatively, rip the Windows crap out and replace both ends with a real OS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895</id>
	<title>Re:Any encrypted transmission protocol actually</title>
	<author>link-error</author>
	<datestamp>1246352700000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>
  Wrong.   FTP has a binary mode.   This is probably the reason his files are missing several k at the destination.   Sending a binary file in ascii mode is the ONLY TIME I've ever had a file not transfer entirely/correctly using FTP.  Unless of course there is a network error/timeout, etc, but the FTP client always errored out in those cases.

  Using SFTP over an already secure network will only slow things down greatly.</htmltext>
<tokenext>Wrong .
FTP has a binary mode .
This is probably the reason his files are missing several k at the destination .
Sending a binary file in ascii mode is the ONLY TIME I 've ever had a file not transfer entirely/correctly using FTP .
Unless of course there is a network error/timeout , etc , but the FTP client always errored out in those cases .
Using SFTP over an already secure network will only slow things down greatly .</tokentext>
<sentencetext>
  Wrong.
FTP has a binary mode.
This is probably the reason his files are missing several k at the destination.
Sending a binary file in ascii mode is the ONLY TIME I've ever had a file not transfer entirely/correctly using FTP.
Unless of course there is a network error/timeout, etc, but the FTP client always errored out in those cases.
Using SFTP over an already secure network will only slow things down greatly.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538299</id>
	<title>Re:TCP?</title>
	<author>nester</author>
	<datestamp>1246379700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you don't know anything, don't post. File sizes in every mainstream OS have byte granularity. Block size is irrelevant.</p></htmltext>
<tokenext>If you do n't know anything , do n't post .
File sizes in every mainstream OS have byte granularity .
Block size is irrelevant .</tokentext>
<sentencetext>If you don't know anything, don't post.
File sizes in every mainstream OS have byte granularity.
Block size is irrelevant.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28541463</id>
	<title>Re:TCP?</title>
	<author>asynchronous13</author>
	<datestamp>1246459020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I just finished updating the checksum routines at my company. Amazingly, they had been using an 8-bit XOR checksum for years (!) on a mission-critical wireless data link. Since this was low-level mission-critical code with lots of proven flight-time, I had to prove conclusively that the new method would, in fact, be better.</p><p><div class="quote"><p>TCP uses a 16-bit checksum, so you have 1 in 65536 chance of an error packet being incorrectly validated as being correct.  To make matters worse, it uses 1's complement instead of 2's complement, so 0x00 and 0xFF are indistinguishable.</p></div><p>It's not as simple as saying 1 in 2^N chance of error for an N-bit checksum. It depends strongly on the specific checksum algorithm, and to a degree the number of bits, length of data packet, and expected bit error rate.

</p><p>For example, 8-bit XOR lets 12\% of 2-bit errors through undetected, and 16-bit XOR only brings that down to 6\%. WAY different than if you expected it to change from 1:256 to 1:65536. But an 8-bit CRC checksum has 1:10^8, and the 16-bit version has 1:10^16 chance of undetected error. Again, WAY different than 1 in 2^N chance.

</p><p>Surprisingly (to me at least), 1's compliment catches *more* errors than does 2's compliment. (the reason being that a pair of bit inversions involving the MSB remains undetected by 2's complement, but is caught by 1's compliment)

</p><p>We decided to go with a 32-bit one's compliment Fletcher checksum -- good compromise between performance and error checking for our application.</p></div>
	</htmltext>
<tokenext>I just finished updating the checksum routines at my company .
Amazingly , they had been using an 8-bit XOR checksum for years ( !
) on a mission-critical wireless data link .
Since this was low-level mission-critical code with lots of proven flight-time , I had to prove conclusively that the new method would , in fact , be better.TCP uses a 16-bit checksum , so you have 1 in 65536 chance of an error packet being incorrectly validated as being correct .
To make matters worse , it uses 1 's complement instead of 2 's complement , so 0x00 and 0xFF are indistinguishable.It 's not as simple as saying 1 in 2 ^ N chance of error for an N-bit checksum .
It depends strongly on the specific checksum algorithm , and to a degree the number of bits , length of data packet , and expected bit error rate .
For example , 8-bit XOR lets 12 \ % of 2-bit errors through undetected , and 16-bit XOR only brings that down to 6 \ % .
WAY different than if you expected it to change from 1 : 256 to 1 : 65536 .
But an 8-bit CRC checksum has 1 : 10 ^ 8 , and the 16-bit version has 1 : 10 ^ 16 chance of undetected error .
Again , WAY different than 1 in 2 ^ N chance .
Surprisingly ( to me at least ) , 1 's compliment catches * more * errors than does 2 's compliment .
( the reason being that a pair of bit inversions involving the MSB remains undetected by 2 's complement , but is caught by 1 's compliment ) We decided to go with a 32-bit one 's compliment Fletcher checksum -- good compromise between performance and error checking for our application .</tokentext>
<sentencetext>I just finished updating the checksum routines at my company.
Amazingly, they had been using an 8-bit XOR checksum for years (!
) on a mission-critical wireless data link.
Since this was low-level mission-critical code with lots of proven flight-time, I had to prove conclusively that the new method would, in fact, be better.TCP uses a 16-bit checksum, so you have 1 in 65536 chance of an error packet being incorrectly validated as being correct.
To make matters worse, it uses 1's complement instead of 2's complement, so 0x00 and 0xFF are indistinguishable.It's not as simple as saying 1 in 2^N chance of error for an N-bit checksum.
It depends strongly on the specific checksum algorithm, and to a degree the number of bits, length of data packet, and expected bit error rate.
For example, 8-bit XOR lets 12\% of 2-bit errors through undetected, and 16-bit XOR only brings that down to 6\%.
WAY different than if you expected it to change from 1:256 to 1:65536.
But an 8-bit CRC checksum has 1:10^8, and the 16-bit version has 1:10^16 chance of undetected error.
Again, WAY different than 1 in 2^N chance.
Surprisingly (to me at least), 1's compliment catches *more* errors than does 2's compliment.
(the reason being that a pair of bit inversions involving the MSB remains undetected by 2's complement, but is caught by 1's compliment)

We decided to go with a 32-bit one's compliment Fletcher checksum -- good compromise between performance and error checking for our application.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531775</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531775</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246387500000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>While others point out, probably correctly, that the problem is probably a binary/ascii conversion, in actuality the error checking on TCP is simply not that good.</p><p>TCP uses a 16-bit checksum, so you have 1 in 65536 chance of an error packet being incorrectly validated as being correct.  To make matters worse, it uses 1's complement instead of 2's complement, so 0x00 and 0xFF are indistinguishable.</p><p>Ethernet has a 32-bit, 2's complement checksum so if you're transmitting over that link-layer you're probably in good shape.  But depending on that from a systems point of view seems risky.</p><p>Much better to only transfer ZIPs and check them at the other end if you only have control over the endpoints.  If you can control the transmission, use a better error-correcting high-level protocol or even a forward-error correction protocol on top of TCP.</p><p>Or just use rsync.</p></htmltext>
<tokenext>While others point out , probably correctly , that the problem is probably a binary/ascii conversion , in actuality the error checking on TCP is simply not that good.TCP uses a 16-bit checksum , so you have 1 in 65536 chance of an error packet being incorrectly validated as being correct .
To make matters worse , it uses 1 's complement instead of 2 's complement , so 0x00 and 0xFF are indistinguishable.Ethernet has a 32-bit , 2 's complement checksum so if you 're transmitting over that link-layer you 're probably in good shape .
But depending on that from a systems point of view seems risky.Much better to only transfer ZIPs and check them at the other end if you only have control over the endpoints .
If you can control the transmission , use a better error-correcting high-level protocol or even a forward-error correction protocol on top of TCP.Or just use rsync .</tokentext>
<sentencetext>While others point out, probably correctly, that the problem is probably a binary/ascii conversion, in actuality the error checking on TCP is simply not that good.TCP uses a 16-bit checksum, so you have 1 in 65536 chance of an error packet being incorrectly validated as being correct.
To make matters worse, it uses 1's complement instead of 2's complement, so 0x00 and 0xFF are indistinguishable.Ethernet has a 32-bit, 2's complement checksum so if you're transmitting over that link-layer you're probably in good shape.
But depending on that from a systems point of view seems risky.Much better to only transfer ZIPs and check them at the other end if you only have control over the endpoints.
If you can control the transmission, use a better error-correcting high-level protocol or even a forward-error correction protocol on top of TCP.Or just use rsync.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532077</id>
	<title>What do you mean a few Kilobytes differnt</title>
	<author>geekoid</author>
	<datestamp>1246388640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Are you just looking at the file size on the disk, or have you done a data comparison?</p><p>If you are just looking at the size as they appear in windows by right clicking at looking a the properties, you are woefully under qualifed to do anything remotly like this and need training.</p><p>There is no reason Windows in and if itself can't do this with FTP.<br>What are you not telling us?</p></htmltext>
<tokenext>Are you just looking at the file size on the disk , or have you done a data comparison ? If you are just looking at the size as they appear in windows by right clicking at looking a the properties , you are woefully under qualifed to do anything remotly like this and need training.There is no reason Windows in and if itself ca n't do this with FTP.What are you not telling us ?</tokentext>
<sentencetext>Are you just looking at the file size on the disk, or have you done a data comparison?If you are just looking at the size as they appear in windows by right clicking at looking a the properties, you are woefully under qualifed to do anything remotly like this and need training.There is no reason Windows in and if itself can't do this with FTP.What are you not telling us?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536725</id>
	<title>answer to the question</title>
	<author>I)\_MaLaClYpSe\_(I</author>
	<datestamp>1246366680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I do also suspect that the CR/LF conversion might be the source of his troubles. Thus, it's not a bug, it's a feature of the ftp protocol. I guess you could simply use binary mode for the ftp transfer. <p>
Now, let's assume that it's not an CR/LF problem but that instead for some unknown reason the ftp transfers get aborted and thus the file size mismatches. </p><p>
Okay, first of all, if you want to guarantee that a file that departed from one system is the very same file after its arrival on another system it is not wise to use the file size for verification, as the two files could have the same length but different contents. Therefore typically md5sum is used. Or better yet, use both MD5 and SHA-1 hashes so nobody could probably ever produce meaningful collisions for both of them at the same time.</p><p>
Now, what programs should be used for the transmission itself? Well, that depends on your requirements: Is confidentiality important or is it really just about integrity and availability? Is speed or link saturation a topic? Like, if your current pipe is like 80\% full, you probably cannot afford to encrypt your data. Otherwise, of course you should except for like if an IPS/IDS maintainer wants to be able to scan the contents. Let's take a look at both possibilities:</p><ul> <li>First: Confidentiality not an issue but bandwidth/speed/IDS is</li></ul><p>
Basically suitable is every tcp data transfer application that does by itself not meddle with the data itself. So this kind of excludes ftp as it can substitute CR/LF (Unix) line brakes with CR (Windows) ASCII text line brakes while transferring data from UNIX to windows and vice versa. But then again, you can use FTP just fine if used in binary mode. However, even the Swiss army knife of network transmissions can be easily used for the purpose of reliably transmitting files from A to B: netcat.</p><p>
nc or nc.exe is available for both Windows and Unix and is often used in the forensics world in manual combination with md5 and/or sha-1 hashes to transmit forensic evidence from e.g. a suspect drive to the examiners workstation. Here the chain of evidence would be maintained by recording a hash of the data on the suspect drive, recording a hash of the data on the examiners workstation after arrival and recording the date, time and contents of the transmission. Note that it might be vital to have a log of what has been transferred when so that it can be proven that you sent some data the other party claims to never having received it.

So, recapping, e.g. netcat, ftp, SMB/CIFS shares, HTTP and any other TCP based file transfer utility could be used. HTTP and FTP could even be easily scanned for viruses/malware during transit. UDP based file transfer utilities could be used as well as long as the implementation does take care of the integrity. As most likely a short script would be used in order to generate logs containing MD5 and SHA-1 hashes on both sides, the time and date of the transfer and the filename, this script could as well easily handle data retransfers in the case of packet loss.

</p><ul> <li>Second an better: confidentiality with some bandwidth and CPU constraints</li></ul><p>
Sorry, this posting by now bores me. So, the recap:</p><p>
Use SSH (SCP), cryptcat (used among others in forensics for the chain of evidence when confidentiality is an issue), HTTPS, SMIME or any other encrypted transfer tool, really. Hell, you could even generate an encrypted PGP file or whatever with a script and pipe it through whatever data transfer application you want. (Like ftp in binary mode<nobr> <wbr></nobr>;) )</p><p>
So, overall, what are needed here are two small scripts that do something like this:</p><p>
On the sending side:
<br> <br>
10 compute SHA-1 / MD5 hash of a file to be transferred (and optionally compress it)
20 send file
30 receive a SHA-1 / MD5 hash of the transferred file from the receiver
40 compare the hashed
50 complete transaction including logging the date, time, filename and hash, if hashed match
60 else goto 20
</p><p>
On the receiving side:
10 receive</p></htmltext>
<tokenext>I do also suspect that the CR/LF conversion might be the source of his troubles .
Thus , it 's not a bug , it 's a feature of the ftp protocol .
I guess you could simply use binary mode for the ftp transfer .
Now , let 's assume that it 's not an CR/LF problem but that instead for some unknown reason the ftp transfers get aborted and thus the file size mismatches .
Okay , first of all , if you want to guarantee that a file that departed from one system is the very same file after its arrival on another system it is not wise to use the file size for verification , as the two files could have the same length but different contents .
Therefore typically md5sum is used .
Or better yet , use both MD5 and SHA-1 hashes so nobody could probably ever produce meaningful collisions for both of them at the same time .
Now , what programs should be used for the transmission itself ?
Well , that depends on your requirements : Is confidentiality important or is it really just about integrity and availability ?
Is speed or link saturation a topic ?
Like , if your current pipe is like 80 \ % full , you probably can not afford to encrypt your data .
Otherwise , of course you should except for like if an IPS/IDS maintainer wants to be able to scan the contents .
Let 's take a look at both possibilities : First : Confidentiality not an issue but bandwidth/speed/IDS is Basically suitable is every tcp data transfer application that does by itself not meddle with the data itself .
So this kind of excludes ftp as it can substitute CR/LF ( Unix ) line brakes with CR ( Windows ) ASCII text line brakes while transferring data from UNIX to windows and vice versa .
But then again , you can use FTP just fine if used in binary mode .
However , even the Swiss army knife of network transmissions can be easily used for the purpose of reliably transmitting files from A to B : netcat .
nc or nc.exe is available for both Windows and Unix and is often used in the forensics world in manual combination with md5 and/or sha-1 hashes to transmit forensic evidence from e.g .
a suspect drive to the examiners workstation .
Here the chain of evidence would be maintained by recording a hash of the data on the suspect drive , recording a hash of the data on the examiners workstation after arrival and recording the date , time and contents of the transmission .
Note that it might be vital to have a log of what has been transferred when so that it can be proven that you sent some data the other party claims to never having received it .
So , recapping , e.g .
netcat , ftp , SMB/CIFS shares , HTTP and any other TCP based file transfer utility could be used .
HTTP and FTP could even be easily scanned for viruses/malware during transit .
UDP based file transfer utilities could be used as well as long as the implementation does take care of the integrity .
As most likely a short script would be used in order to generate logs containing MD5 and SHA-1 hashes on both sides , the time and date of the transfer and the filename , this script could as well easily handle data retransfers in the case of packet loss .
Second an better : confidentiality with some bandwidth and CPU constraints Sorry , this posting by now bores me .
So , the recap : Use SSH ( SCP ) , cryptcat ( used among others in forensics for the chain of evidence when confidentiality is an issue ) , HTTPS , SMIME or any other encrypted transfer tool , really .
Hell , you could even generate an encrypted PGP file or whatever with a script and pipe it through whatever data transfer application you want .
( Like ftp in binary mode ; ) ) So , overall , what are needed here are two small scripts that do something like this : On the sending side : 10 compute SHA-1 / MD5 hash of a file to be transferred ( and optionally compress it ) 20 send file 30 receive a SHA-1 / MD5 hash of the transferred file from the receiver 40 compare the hashed 50 complete transaction including logging the date , time , filename and hash , if hashed match 60 else goto 20 On the receiving side : 10 receive</tokentext>
<sentencetext>I do also suspect that the CR/LF conversion might be the source of his troubles.
Thus, it's not a bug, it's a feature of the ftp protocol.
I guess you could simply use binary mode for the ftp transfer.
Now, let's assume that it's not an CR/LF problem but that instead for some unknown reason the ftp transfers get aborted and thus the file size mismatches.
Okay, first of all, if you want to guarantee that a file that departed from one system is the very same file after its arrival on another system it is not wise to use the file size for verification, as the two files could have the same length but different contents.
Therefore typically md5sum is used.
Or better yet, use both MD5 and SHA-1 hashes so nobody could probably ever produce meaningful collisions for both of them at the same time.
Now, what programs should be used for the transmission itself?
Well, that depends on your requirements: Is confidentiality important or is it really just about integrity and availability?
Is speed or link saturation a topic?
Like, if your current pipe is like 80\% full, you probably cannot afford to encrypt your data.
Otherwise, of course you should except for like if an IPS/IDS maintainer wants to be able to scan the contents.
Let's take a look at both possibilities: First: Confidentiality not an issue but bandwidth/speed/IDS is
Basically suitable is every tcp data transfer application that does by itself not meddle with the data itself.
So this kind of excludes ftp as it can substitute CR/LF (Unix) line brakes with CR (Windows) ASCII text line brakes while transferring data from UNIX to windows and vice versa.
But then again, you can use FTP just fine if used in binary mode.
However, even the Swiss army knife of network transmissions can be easily used for the purpose of reliably transmitting files from A to B: netcat.
nc or nc.exe is available for both Windows and Unix and is often used in the forensics world in manual combination with md5 and/or sha-1 hashes to transmit forensic evidence from e.g.
a suspect drive to the examiners workstation.
Here the chain of evidence would be maintained by recording a hash of the data on the suspect drive, recording a hash of the data on the examiners workstation after arrival and recording the date, time and contents of the transmission.
Note that it might be vital to have a log of what has been transferred when so that it can be proven that you sent some data the other party claims to never having received it.
So, recapping, e.g.
netcat, ftp, SMB/CIFS shares, HTTP and any other TCP based file transfer utility could be used.
HTTP and FTP could even be easily scanned for viruses/malware during transit.
UDP based file transfer utilities could be used as well as long as the implementation does take care of the integrity.
As most likely a short script would be used in order to generate logs containing MD5 and SHA-1 hashes on both sides, the time and date of the transfer and the filename, this script could as well easily handle data retransfers in the case of packet loss.
Second an better: confidentiality with some bandwidth and CPU constraints
Sorry, this posting by now bores me.
So, the recap:
Use SSH (SCP), cryptcat (used among others in forensics for the chain of evidence when confidentiality is an issue), HTTPS, SMIME or any other encrypted transfer tool, really.
Hell, you could even generate an encrypted PGP file or whatever with a script and pipe it through whatever data transfer application you want.
(Like ftp in binary mode ;) )
So, overall, what are needed here are two small scripts that do something like this:
On the sending side:
 
10 compute SHA-1 / MD5 hash of a file to be transferred (and optionally compress it)
20 send file
30 receive a SHA-1 / MD5 hash of the transferred file from the receiver
40 compare the hashed
50 complete transaction including logging the date, time, filename and hash, if hashed match
60 else goto 20

On the receiving side:
10 receive</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536711</id>
	<title>IBM's MQ</title>
	<author>Anonymous</author>
	<datestamp>1246366620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You want IBM's MQ software.  Two MQ Servers to talk to one another.<br>It's a bit pricy, but guaranteed delivery.</p></htmltext>
<tokenext>You want IBM 's MQ software .
Two MQ Servers to talk to one another.It 's a bit pricy , but guaranteed delivery .</tokentext>
<sentencetext>You want IBM's MQ software.
Two MQ Servers to talk to one another.It's a bit pricy, but guaranteed delivery.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539839</id>
	<title>Run BSD code ftw ;-)</title>
	<author>jonaskoelker</author>
	<datestamp>1246442280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>try the Windows command line FTP</p></div><p>I vote AYE on this!  Everyone knows that BSD code is rock solid<nobr> <wbr></nobr>;-)</p></div>
	</htmltext>
<tokenext>try the Windows command line FTPI vote AYE on this !
Everyone knows that BSD code is rock solid ; - )</tokentext>
<sentencetext>try the Windows command line FTPI vote AYE on this!
Everyone knows that BSD code is rock solid ;-)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531239</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533339</id>
	<title>Re:You're kidding, aren't you??</title>
	<author>Dravik</author>
	<datestamp>1246393560000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>Mission critical means that you need to get it done even if someone else isn't getting their job done.  Standing around in a huff and stomping your feet means that the mission critical information isn't getting moved.  What he needs to do is find a way to accomplish his mission despite the difficulties, and then document the problems so they can be addressed.</htmltext>
<tokenext>Mission critical means that you need to get it done even if someone else is n't getting their job done .
Standing around in a huff and stomping your feet means that the mission critical information is n't getting moved .
What he needs to do is find a way to accomplish his mission despite the difficulties , and then document the problems so they can be addressed .</tokentext>
<sentencetext>Mission critical means that you need to get it done even if someone else isn't getting their job done.
Standing around in a huff and stomping your feet means that the mission critical information isn't getting moved.
What he needs to do is find a way to accomplish his mission despite the difficulties, and then document the problems so they can be addressed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533065</id>
	<title>kermit</title>
	<author>Anonymous</author>
	<datestamp>1246392300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Do you mean a transfer protocol like kermit?</htmltext>
<tokenext>Do you mean a transfer protocol like kermit ?</tokentext>
<sentencetext>Do you mean a transfer protocol like kermit?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530145</id>
	<title>anonymous coward</title>
	<author>Anonymous</author>
	<datestamp>1246383120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>create checksums?<nobr> <wbr></nobr>.. md5/sfv for e.g.</p></htmltext>
<tokenext>create checksums ?
.. md5/sfv for e.g .</tokentext>
<sentencetext>create checksums?
.. md5/sfv for e.g.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535877</id>
	<title>Sounds like better FEC is needed</title>
	<author>likecheese</author>
	<datestamp>1246362240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I was once in a startup trying to deliver streaming video to tablets/laptops at sporting events via 802.11 wireless networks.  Within 30-50 feet of an access point, it worked great, but any further than that and packet loss was too high to decode the video stream.  Before our investors pulled the plug, we looked into technology from a company called <a href="http://www.digitalfountain.com/" title="digitalfountain.com" rel="nofollow">Digital Fountain</a> [digitalfountain.com].  They use a type of forward error correction called <a href="http://en.wikipedia.org/wiki/Raptor\_code" title="wikipedia.org" rel="nofollow">raptor codes</a> [wikipedia.org] to make data transmission high resilient to packet loss on unreliable networks.  It's a commercial product, but I assume the OP's employer can afford it if they're transmitting "mission critical" files for the government.</htmltext>
<tokenext>I was once in a startup trying to deliver streaming video to tablets/laptops at sporting events via 802.11 wireless networks .
Within 30-50 feet of an access point , it worked great , but any further than that and packet loss was too high to decode the video stream .
Before our investors pulled the plug , we looked into technology from a company called Digital Fountain [ digitalfountain.com ] .
They use a type of forward error correction called raptor codes [ wikipedia.org ] to make data transmission high resilient to packet loss on unreliable networks .
It 's a commercial product , but I assume the OP 's employer can afford it if they 're transmitting " mission critical " files for the government .</tokentext>
<sentencetext>I was once in a startup trying to deliver streaming video to tablets/laptops at sporting events via 802.11 wireless networks.
Within 30-50 feet of an access point, it worked great, but any further than that and packet loss was too high to decode the video stream.
Before our investors pulled the plug, we looked into technology from a company called Digital Fountain [digitalfountain.com].
They use a type of forward error correction called raptor codes [wikipedia.org] to make data transmission high resilient to packet loss on unreliable networks.
It's a commercial product, but I assume the OP's employer can afford it if they're transmitting "mission critical" files for the government.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533995</id>
	<title>Re:rsync</title>
	<author>Anonymous</author>
	<datestamp>1246353120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jsp</p><p>Delta Copy is a wrapper for rsync that works on Windows boxen.</p></htmltext>
<tokenext>http : //www.aboutmyip.com/AboutMyXApp/DeltaCopy.jspDelta Copy is a wrapper for rsync that works on Windows boxen .</tokentext>
<sentencetext>http://www.aboutmyip.com/AboutMyXApp/DeltaCopy.jspDelta Copy is a wrapper for rsync that works on Windows boxen.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530399</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531623</id>
	<title>Size descrepency</title>
	<author>LaminatorX</author>
	<datestamp>1246387020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>First off, I second the recommendation for rsync.  This is what it's for. It's also easy to do over a SSH tunnel or similar.</p><p>As far as your size discrepancy goes, it's possible that such a small variation could be accounted for by different block sizes on the source and destination volumes. The data may in fact be identical, but the two different volumes may need to allocate a slightly different amount of disc space to store it.</p><p>rsync does hash checks as part of its normal operation, but if you really wanted to be methodical, you could have a script rsync to three different directories and then compare hashes on all copies.  This may or may not be overkill, depending on your mission.</p></htmltext>
<tokenext>First off , I second the recommendation for rsync .
This is what it 's for .
It 's also easy to do over a SSH tunnel or similar.As far as your size discrepancy goes , it 's possible that such a small variation could be accounted for by different block sizes on the source and destination volumes .
The data may in fact be identical , but the two different volumes may need to allocate a slightly different amount of disc space to store it.rsync does hash checks as part of its normal operation , but if you really wanted to be methodical , you could have a script rsync to three different directories and then compare hashes on all copies .
This may or may not be overkill , depending on your mission .</tokentext>
<sentencetext>First off, I second the recommendation for rsync.
This is what it's for.
It's also easy to do over a SSH tunnel or similar.As far as your size discrepancy goes, it's possible that such a small variation could be accounted for by different block sizes on the source and destination volumes.
The data may in fact be identical, but the two different volumes may need to allocate a slightly different amount of disc space to store it.rsync does hash checks as part of its normal operation, but if you really wanted to be methodical, you could have a script rsync to three different directories and then compare hashes on all copies.
This may or may not be overkill, depending on your mission.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530799</id>
	<title>Re:Jesus protocol</title>
	<author>CarpetShark</author>
	<datestamp>1246384740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yeah, but having to drive nails through your hands and count the droplets before entering the count as a one time pad gets old after a while.</p></htmltext>
<tokenext>Yeah , but having to drive nails through your hands and count the droplets before entering the count as a one time pad gets old after a while .</tokentext>
<sentencetext>Yeah, but having to drive nails through your hands and count the droplets before entering the count as a one time pad gets old after a while.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530163</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530165</id>
	<title>Bit torrent</title>
	<author>Anonymous</author>
	<datestamp>1246383180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Automatic hashing of transferred pieces, ability to verify the entire package after transfer, higher performance if hosting on multiple machines...</p><p>I'm sure you can setup an adhoc private setup... Maybe even utorrent between two machines.</p></htmltext>
<tokenext>Automatic hashing of transferred pieces , ability to verify the entire package after transfer , higher performance if hosting on multiple machines...I 'm sure you can setup an adhoc private setup... Maybe even utorrent between two machines .</tokentext>
<sentencetext>Automatic hashing of transferred pieces, ability to verify the entire package after transfer, higher performance if hosting on multiple machines...I'm sure you can setup an adhoc private setup... Maybe even utorrent between two machines.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531911</id>
	<title>hash them, just for fun</title>
	<author>cats-paw</author>
	<datestamp>1246388040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Use MD5 or some other relatively strong checksum (CRC-32) too, just to be \_absolutely\_ sure that you didn't get any errors.   It's a paranoia indulgence though if you are using TCP and rsync.</p></htmltext>
<tokenext>Use MD5 or some other relatively strong checksum ( CRC-32 ) too , just to be \ _absolutely \ _ sure that you did n't get any errors .
It 's a paranoia indulgence though if you are using TCP and rsync .</tokentext>
<sentencetext>Use MD5 or some other relatively strong checksum (CRC-32) too, just to be \_absolutely\_ sure that you didn't get any errors.
It's a paranoia indulgence though if you are using TCP and rsync.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151</id>
	<title>Any encrypted transmission protocol actually</title>
	<author>Anonymous</author>
	<datestamp>1246383180000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext><p>SFTP should do since the communications are encrypted, if something changes along the way it should be rejected by the other end. HTTPS and any other protocol-over-SSL should do.</p><p>FTP is a plain-text protocol so if something changes along the way it won't give you any issues.</p></htmltext>
<tokenext>SFTP should do since the communications are encrypted , if something changes along the way it should be rejected by the other end .
HTTPS and any other protocol-over-SSL should do.FTP is a plain-text protocol so if something changes along the way it wo n't give you any issues .</tokentext>
<sentencetext>SFTP should do since the communications are encrypted, if something changes along the way it should be rejected by the other end.
HTTPS and any other protocol-over-SSL should do.FTP is a plain-text protocol so if something changes along the way it won't give you any issues.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531235</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246385880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>great point.</htmltext>
<tokenext>great point .</tokentext>
<sentencetext>great point.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532117</id>
	<title>MQ</title>
	<author>eap</author>
	<datestamp>1246388760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you need guaranteed, fault tolerant, one-time message delivery you could use IBM's Websphere MQ.  It is expensive bloaty, but it gets the job done and will tolerate intermittent connectivity problems.  It runs on every platform and there are client API's for many languages.</p><p>
&nbsp; </p><p>Place an MQ server at each end, then have the client enqueue the message at one end and a listener dequeue at the other end.  If the link or other host is down, the clients can still send messages which are stored and delivered when the comm. link comes back up.  Transactions and rollback are supported, and large files are automatically segmented and reconstructed by the system.</p><p>
&nbsp; </p><p>You can configure it to send message receipts, prioritize messages, and report any failures to a dead letter queue.</p><p>
&nbsp; &nbsp; </p><p>There may be other brands of middleware that do this just as well for free.  WMQ is just the one I'm most familiar with (I don't work for IBM).</p></htmltext>
<tokenext>If you need guaranteed , fault tolerant , one-time message delivery you could use IBM 's Websphere MQ .
It is expensive bloaty , but it gets the job done and will tolerate intermittent connectivity problems .
It runs on every platform and there are client API 's for many languages .
  Place an MQ server at each end , then have the client enqueue the message at one end and a listener dequeue at the other end .
If the link or other host is down , the clients can still send messages which are stored and delivered when the comm .
link comes back up .
Transactions and rollback are supported , and large files are automatically segmented and reconstructed by the system .
  You can configure it to send message receipts , prioritize messages , and report any failures to a dead letter queue .
    There may be other brands of middleware that do this just as well for free .
WMQ is just the one I 'm most familiar with ( I do n't work for IBM ) .</tokentext>
<sentencetext>If you need guaranteed, fault tolerant, one-time message delivery you could use IBM's Websphere MQ.
It is expensive bloaty, but it gets the job done and will tolerate intermittent connectivity problems.
It runs on every platform and there are client API's for many languages.
  Place an MQ server at each end, then have the client enqueue the message at one end and a listener dequeue at the other end.
If the link or other host is down, the clients can still send messages which are stored and delivered when the comm.
link comes back up.
Transactions and rollback are supported, and large files are automatically segmented and reconstructed by the system.
  You can configure it to send message receipts, prioritize messages, and report any failures to a dead letter queue.
    There may be other brands of middleware that do this just as well for free.
WMQ is just the one I'm most familiar with (I don't work for IBM).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536145</id>
	<title>Re:You're kidding, aren't you??</title>
	<author>Anonymous</author>
	<datestamp>1246363560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If NASA can send firmware updates through space, I'm sure there's an application that can handle intermittent network issues as evidenced by all the other replies.</p></htmltext>
<tokenext>If NASA can send firmware updates through space , I 'm sure there 's an application that can handle intermittent network issues as evidenced by all the other replies .</tokentext>
<sentencetext>If NASA can send firmware updates through space, I'm sure there's an application that can handle intermittent network issues as evidenced by all the other replies.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532113</id>
	<title>Re:Line endings!</title>
	<author>Anonymous</author>
	<datestamp>1246388700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I agree that the problem is probably that text mode is being used instead of binary. If that's not the case look at C-Kermit. It is a very robust file transfer protocol updated from the days when everything was sent over very unreliable modem connections. NASA is still using it today for some of their space communications.</p></htmltext>
<tokenext>I agree that the problem is probably that text mode is being used instead of binary .
If that 's not the case look at C-Kermit .
It is a very robust file transfer protocol updated from the days when everything was sent over very unreliable modem connections .
NASA is still using it today for some of their space communications .</tokentext>
<sentencetext>I agree that the problem is probably that text mode is being used instead of binary.
If that's not the case look at C-Kermit.
It is a very robust file transfer protocol updated from the days when everything was sent over very unreliable modem connections.
NASA is still using it today for some of their space communications.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530955</id>
	<title>Stuffit or WinRAR</title>
	<author>mlts</author>
	<datestamp>1246385100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I used to have a similar problem over another connection, where even more advanced file copy utilities would say the file was copied, but a 2-4k chunk would be missing.  What I did to solve the problem was to use an archiving utility that supported adding ECC records and install it on both endpoints.  Then, I'd just archive the files I need, send them over the faulty link, and usually the ECC records were able to correct any errors that did crop up during the transfer when extracted on the destination machine.</p><p>I did this manually, but I don't think it would be too difficult to make a scheduled task that would check for files, use the command line of an archive utility to generate a temp archive, sling the archive across, then the machine on the other side of the link extract the files and if the corruption was too great for the ECC records in the archive, to give some type of warning or notice to someone.</p><p>Of course, this is not fixing anything on the network layer, so maybe running either PPP over SSH or a VPN link directly from one machine to another might help.</p></htmltext>
<tokenext>I used to have a similar problem over another connection , where even more advanced file copy utilities would say the file was copied , but a 2-4k chunk would be missing .
What I did to solve the problem was to use an archiving utility that supported adding ECC records and install it on both endpoints .
Then , I 'd just archive the files I need , send them over the faulty link , and usually the ECC records were able to correct any errors that did crop up during the transfer when extracted on the destination machine.I did this manually , but I do n't think it would be too difficult to make a scheduled task that would check for files , use the command line of an archive utility to generate a temp archive , sling the archive across , then the machine on the other side of the link extract the files and if the corruption was too great for the ECC records in the archive , to give some type of warning or notice to someone.Of course , this is not fixing anything on the network layer , so maybe running either PPP over SSH or a VPN link directly from one machine to another might help .</tokentext>
<sentencetext>I used to have a similar problem over another connection, where even more advanced file copy utilities would say the file was copied, but a 2-4k chunk would be missing.
What I did to solve the problem was to use an archiving utility that supported adding ECC records and install it on both endpoints.
Then, I'd just archive the files I need, send them over the faulty link, and usually the ECC records were able to correct any errors that did crop up during the transfer when extracted on the destination machine.I did this manually, but I don't think it would be too difficult to make a scheduled task that would check for files, use the command line of an archive utility to generate a temp archive, sling the archive across, then the machine on the other side of the link extract the files and if the corruption was too great for the ECC records in the archive, to give some type of warning or notice to someone.Of course, this is not fixing anything on the network layer, so maybe running either PPP over SSH or a VPN link directly from one machine to another might help.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530531</id>
	<title>Windows FTP sucks</title>
	<author>Anonymous</author>
	<datestamp>1246384080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I had this same problem but with cable modem internet on one end and DSL on the other.<br>I am guessing you are using the windows ftp command in a batch file. Problem is, if the line is interruped, ftp doesn't care and carries on in your batch file as if the transfer completed 100\%</p><p>I purchased one copy of WS\_FTP Pro by Ipswitch and using the bacth scripting function created a script that will loop until the file is sent entirly. It's low cost and works great.</p></htmltext>
<tokenext>I had this same problem but with cable modem internet on one end and DSL on the other.I am guessing you are using the windows ftp command in a batch file .
Problem is , if the line is interruped , ftp does n't care and carries on in your batch file as if the transfer completed 100 \ % I purchased one copy of WS \ _FTP Pro by Ipswitch and using the bacth scripting function created a script that will loop until the file is sent entirly .
It 's low cost and works great .</tokentext>
<sentencetext>I had this same problem but with cable modem internet on one end and DSL on the other.I am guessing you are using the windows ftp command in a batch file.
Problem is, if the line is interruped, ftp doesn't care and carries on in your batch file as if the transfer completed 100\%I purchased one copy of WS\_FTP Pro by Ipswitch and using the bacth scripting function created a script that will loop until the file is sent entirly.
It's low cost and works great.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489</id>
	<title>Re:TCP?</title>
	<author>causality</author>
	<datestamp>1246386600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>The only times I've seen FTP report a successful file transfer and have a file discrepency is when a binary file has been transferred in ASCII mode and the CR/LF sequences are being swapped for just CRs, or visa versa.  Nothing wrong with the protocol, PEBKAC...</p></div><p>Since ASCII files are also ultimately represented as particular sequences of binary data, why does FTP even have an ASCII transfer mode?  Or, why would you want to download a file and receive anything other than an exact duplicate of the file that was sitting on the server?
<br> <br>
I know that Windows uses CR/LF for line termination and *nix uses just LF.  That's a very minor inconvenience at worst, though my reasoning should hold up even if it were a big deal.  Most (all?) *nix text editors I've ever worked with had no problem reading both formats, and little standalone utilities to convert the formats are readily available and have been for some time now.  Additionally, on Windows, Notepad is the only app I've ever seen that had trouble with the *nix format (the built-in Wordpad can handle it fine).  So I don't understand why the lower-level transfer protocol is the best place to include this functionality, as it really doesn't seem to belong there.  It just seems like it's not the job of a file transfer protocol to concern itself with what an independent, unrelated application can or cannot do with the file after it's transferred.</p></div>
	</htmltext>
<tokenext>The only times I 've seen FTP report a successful file transfer and have a file discrepency is when a binary file has been transferred in ASCII mode and the CR/LF sequences are being swapped for just CRs , or visa versa .
Nothing wrong with the protocol , PEBKAC...Since ASCII files are also ultimately represented as particular sequences of binary data , why does FTP even have an ASCII transfer mode ?
Or , why would you want to download a file and receive anything other than an exact duplicate of the file that was sitting on the server ?
I know that Windows uses CR/LF for line termination and * nix uses just LF .
That 's a very minor inconvenience at worst , though my reasoning should hold up even if it were a big deal .
Most ( all ?
) * nix text editors I 've ever worked with had no problem reading both formats , and little standalone utilities to convert the formats are readily available and have been for some time now .
Additionally , on Windows , Notepad is the only app I 've ever seen that had trouble with the * nix format ( the built-in Wordpad can handle it fine ) .
So I do n't understand why the lower-level transfer protocol is the best place to include this functionality , as it really does n't seem to belong there .
It just seems like it 's not the job of a file transfer protocol to concern itself with what an independent , unrelated application can or can not do with the file after it 's transferred .</tokentext>
<sentencetext>The only times I've seen FTP report a successful file transfer and have a file discrepency is when a binary file has been transferred in ASCII mode and the CR/LF sequences are being swapped for just CRs, or visa versa.
Nothing wrong with the protocol, PEBKAC...Since ASCII files are also ultimately represented as particular sequences of binary data, why does FTP even have an ASCII transfer mode?
Or, why would you want to download a file and receive anything other than an exact duplicate of the file that was sitting on the server?
I know that Windows uses CR/LF for line termination and *nix uses just LF.
That's a very minor inconvenience at worst, though my reasoning should hold up even if it were a big deal.
Most (all?
) *nix text editors I've ever worked with had no problem reading both formats, and little standalone utilities to convert the formats are readily available and have been for some time now.
Additionally, on Windows, Notepad is the only app I've ever seen that had trouble with the *nix format (the built-in Wordpad can handle it fine).
So I don't understand why the lower-level transfer protocol is the best place to include this functionality, as it really doesn't seem to belong there.
It just seems like it's not the job of a file transfer protocol to concern itself with what an independent, unrelated application can or cannot do with the file after it's transferred.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531063</id>
	<title>synchronous/asynchronous?</title>
	<author>tero</author>
	<datestamp>1246385340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Does your file have to be transferred in-synchro?</p><p>Otherwise you might want to look into Message Oriented Middleware, things like MQ Series or in worst case scenario, even Microsoft MQ. There are plenty of options.<br>This would allow you to put policies on the messages, handle routing (in case you need to deliver to different recipients), guarantee delivery at least once, do type conversions/transformations etc.</p></htmltext>
<tokenext>Does your file have to be transferred in-synchro ? Otherwise you might want to look into Message Oriented Middleware , things like MQ Series or in worst case scenario , even Microsoft MQ .
There are plenty of options.This would allow you to put policies on the messages , handle routing ( in case you need to deliver to different recipients ) , guarantee delivery at least once , do type conversions/transformations etc .</tokentext>
<sentencetext>Does your file have to be transferred in-synchro?Otherwise you might want to look into Message Oriented Middleware, things like MQ Series or in worst case scenario, even Microsoft MQ.
There are plenty of options.This would allow you to put policies on the messages, handle routing (in case you need to deliver to different recipients), guarantee delivery at least once, do type conversions/transformations etc.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542437</id>
	<title>Re:TCP?</title>
	<author>causality</author>
	<datestamp>1246463580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>I'm sorry, but I've worked in this area for years. I was responsible for moving data and source files to and from Unix to DOS to VMS to OSs that are even deader than VMS</p></div></blockquote><p>
Sorry, but if that applied to me, I would say "hey, the vast majority of people don't need to do this, so this is (relatively) uniquely my problem and I should find my own solution, such as conversion programs".  What I would not say is "hey, I need to modify a standard protocol that everyone uses to fit my (relatively) unique problem even though most of the users of that protocol don't need this functionality."
<br> <br>
Now, since FTP already has this functionality, there's nothing wrong with using it.  But that's a far cry from saying that this is really the job of a transport protocol or that it was really a good design decision to put it there.  The correct solution for this problem is a standardized way to represent data or at the very least, the capability of recognizing multiple formats.  Really, FTP worrying about this would be a little like Ethernet trying to detect and transcode streaming video.  If I submitted a serious proposal that we modify Ethernet to transcode streaming video, I'd be told that this functionality does not belong at the link layer and that it's the application's problem to worry about this.
<br> <br>
The crux of the disagreement is this:  some people think that their convenience overrides what would otherwise be recognized as a poor or at least questionable design decision.  Other people think that the soundness of a design decision should come first and convenience should be a secondary concern, <i>particularly</i> when there are other, quite viable options for handling the problem.  I am in the latter group.</p></div>
	</htmltext>
<tokenext>I 'm sorry , but I 've worked in this area for years .
I was responsible for moving data and source files to and from Unix to DOS to VMS to OSs that are even deader than VMS Sorry , but if that applied to me , I would say " hey , the vast majority of people do n't need to do this , so this is ( relatively ) uniquely my problem and I should find my own solution , such as conversion programs " .
What I would not say is " hey , I need to modify a standard protocol that everyone uses to fit my ( relatively ) unique problem even though most of the users of that protocol do n't need this functionality .
" Now , since FTP already has this functionality , there 's nothing wrong with using it .
But that 's a far cry from saying that this is really the job of a transport protocol or that it was really a good design decision to put it there .
The correct solution for this problem is a standardized way to represent data or at the very least , the capability of recognizing multiple formats .
Really , FTP worrying about this would be a little like Ethernet trying to detect and transcode streaming video .
If I submitted a serious proposal that we modify Ethernet to transcode streaming video , I 'd be told that this functionality does not belong at the link layer and that it 's the application 's problem to worry about this .
The crux of the disagreement is this : some people think that their convenience overrides what would otherwise be recognized as a poor or at least questionable design decision .
Other people think that the soundness of a design decision should come first and convenience should be a secondary concern , particularly when there are other , quite viable options for handling the problem .
I am in the latter group .</tokentext>
<sentencetext>I'm sorry, but I've worked in this area for years.
I was responsible for moving data and source files to and from Unix to DOS to VMS to OSs that are even deader than VMS
Sorry, but if that applied to me, I would say "hey, the vast majority of people don't need to do this, so this is (relatively) uniquely my problem and I should find my own solution, such as conversion programs".
What I would not say is "hey, I need to modify a standard protocol that everyone uses to fit my (relatively) unique problem even though most of the users of that protocol don't need this functionality.
"
 
Now, since FTP already has this functionality, there's nothing wrong with using it.
But that's a far cry from saying that this is really the job of a transport protocol or that it was really a good design decision to put it there.
The correct solution for this problem is a standardized way to represent data or at the very least, the capability of recognizing multiple formats.
Really, FTP worrying about this would be a little like Ethernet trying to detect and transcode streaming video.
If I submitted a serious proposal that we modify Ethernet to transcode streaming video, I'd be told that this functionality does not belong at the link layer and that it's the application's problem to worry about this.
The crux of the disagreement is this:  some people think that their convenience overrides what would otherwise be recognized as a poor or at least questionable design decision.
Other people think that the soundness of a design decision should come first and convenience should be a secondary concern, particularly when there are other, quite viable options for handling the problem.
I am in the latter group.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533887</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531743</id>
	<title>FTP + XCRC</title>
	<author>Loki\_1929</author>
	<datestamp>1246387440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's built in and it works. You can get something that's theoretically more efficient with a lot of work, but this is quick, cheap, and simple. Best of all, it actually works.</p><p>The client and server each run a checksum against what's on either end after a "successful" transfer. If the xcrc fails, delete and re-send. It's really that easy. If efficiency is an issue, just enable resuming on the client end.</p><p>What a simple question. Your problem is solved with about 20 minutes of work/setup/testing and a budget equal to whatever you get paid for 20 minutes worth of work.</p></htmltext>
<tokenext>It 's built in and it works .
You can get something that 's theoretically more efficient with a lot of work , but this is quick , cheap , and simple .
Best of all , it actually works.The client and server each run a checksum against what 's on either end after a " successful " transfer .
If the xcrc fails , delete and re-send .
It 's really that easy .
If efficiency is an issue , just enable resuming on the client end.What a simple question .
Your problem is solved with about 20 minutes of work/setup/testing and a budget equal to whatever you get paid for 20 minutes worth of work .</tokentext>
<sentencetext>It's built in and it works.
You can get something that's theoretically more efficient with a lot of work, but this is quick, cheap, and simple.
Best of all, it actually works.The client and server each run a checksum against what's on either end after a "successful" transfer.
If the xcrc fails, delete and re-send.
It's really that easy.
If efficiency is an issue, just enable resuming on the client end.What a simple question.
Your problem is solved with about 20 minutes of work/setup/testing and a budget equal to whatever you get paid for 20 minutes worth of work.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539085</id>
	<title>Binary transfers?</title>
	<author>mathew7</author>
	<datestamp>1246389180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Since before I started working here, they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals.</p></div><p>Are you sure you are using BINARY transfers? FTP allows "text" tranfers which can transform the CR+LF pair into 1 byte (CR I think). On large files, you could end-up with several KB missing. This transformation actually depends on client and server, not OS (although it was created because of Windows - Unix conventions).</p><p>Regarding what others have said, I don't see how TCP checksumming could affect the file unless a specific attack is made. Even then, it's hard to block the original TCP packet, and altering it will make the receiver transmit a "retransmission request". (I said hard, not impossible)</p></div>
	</htmltext>
<tokenext>Since before I started working here , they 've been using FTP to upload the files , but many times the copied files are a few kilobytes smaller than the originals.Are you sure you are using BINARY transfers ?
FTP allows " text " tranfers which can transform the CR + LF pair into 1 byte ( CR I think ) .
On large files , you could end-up with several KB missing .
This transformation actually depends on client and server , not OS ( although it was created because of Windows - Unix conventions ) .Regarding what others have said , I do n't see how TCP checksumming could affect the file unless a specific attack is made .
Even then , it 's hard to block the original TCP packet , and altering it will make the receiver transmit a " retransmission request " .
( I said hard , not impossible )</tokentext>
<sentencetext>Since before I started working here, they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals.Are you sure you are using BINARY transfers?
FTP allows "text" tranfers which can transform the CR+LF pair into 1 byte (CR I think).
On large files, you could end-up with several KB missing.
This transformation actually depends on client and server, not OS (although it was created because of Windows - Unix conventions).Regarding what others have said, I don't see how TCP checksumming could affect the file unless a specific attack is made.
Even then, it's hard to block the original TCP packet, and altering it will make the receiver transmit a "retransmission request".
(I said hard, not impossible)
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28547671</id>
	<title>Re:TCP?</title>
	<author>Obfuscant</author>
	<datestamp>1246480140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>Sorry, but if that applied to me, I would say "hey, the vast majority of people don't need to do this, so this is (relatively) uniquely my problem and I should find my own solution, such as conversion programs".</i> <p>
The problem is that the vast majority of people wouldn't know when to look for the problem and wouldn't know how to solve it when it appeared. The BEST place to solve this kind of problem is where both ends know it exists and how to solve it automatically. E.g., in FTP, where the server knows about the host's file system oddities and the client knows the client's.</p><p>
I didn't ask FTP to deal with this, it was dealing with this a long time before I used it. Apparently it solved a LOT of people's problems, not just mine.</p><p>
<i>Now, since FTP already has this functionality, there's nothing wrong with using it. But that's a far cry from saying that this is really the job of a transport protocol or that it was really a good design decision to put it there.</i> </p><p>
That's right. The fact that FTP does it is not an argument that it is the best place to do it. The fact that FTP involves a server that knows about the file system it reads and writes files to, and a client that knows about the file system IT reads and writes files to, is why it is the best place to take care of the conversion. It is stupid for a program designed to transport a certain kind of file from one OS to another to simply ignore the fact that that certain kind of file needs to be converted for use.</p><p>
If you don't want FTP converting things for you automatically, use BIN mode for all your transfers. I like the fact that I don't have to worry about what format the stupid text file is in when I move data around automatically.</p><p>
<i>Really, FTP worrying about this would be a little like Ethernet trying to detect and transcode streaming video.</i> </p><p>
Patently absurd. Ethernet is a hardware layer; FTP is a software layer. Ethernet has no concept of what it carries; FTP KNOWS the file structures because it has to.</p><p><nobr> <wbr></nobr><i>... I'd be told that this functionality does not belong at the link layer and that it's the application's problem to worry about this.</i> </p><p>
That's right. And FTP is an APPLICATION. It is THE ONLY application that knows what the source and destination formats are and how to convert them. That makes FTP the right place to deal with the conversion. We aren't just talking about CRLF/NL differences, remember?</p><p>
<i>The crux of the disagreement is this: some people think that their convenience overrides what would otherwise be recognized as a poor or at least questionable design decision.</i> </p><p>
No, the crux is that some people are very limited in the experiences they have with data management and transport and assume that everything they talk to is just like what they use at home, and thus no conversions are necessary. In those few cases when they are necessary, they assume that their usage of the computer (download a few files) is what everyone else is doing, and that it is simpler to use a standalone converter to convert the "few files". This leads them to THINK that the FTP design decision was poor, when it really is their understanding of the scope of the problem that is poor.</p><p>
<i>Other people think that the soundness of a design decision should come first and convenience should be a secondary concern, particularly when there are other, quite viable options for handling the problem.</i> </p><p>
The other options are not that viable when you are dealing with large volumes of data automatically. The design decision is sound because it is both doing the work where it can be done automatically AND makes life a lot more convenient even for people who have no idea that there would otherwise be a problem. </p><p>
It is patently stupid to force people to make an additional step to convert a file from an "oddball OS" structure into something usable when the transport software can do it for them. If you want an analogy, it is no different than an email program that forces</p></htmltext>
<tokenext>Sorry , but if that applied to me , I would say " hey , the vast majority of people do n't need to do this , so this is ( relatively ) uniquely my problem and I should find my own solution , such as conversion programs " .
The problem is that the vast majority of people would n't know when to look for the problem and would n't know how to solve it when it appeared .
The BEST place to solve this kind of problem is where both ends know it exists and how to solve it automatically .
E.g. , in FTP , where the server knows about the host 's file system oddities and the client knows the client 's .
I did n't ask FTP to deal with this , it was dealing with this a long time before I used it .
Apparently it solved a LOT of people 's problems , not just mine .
Now , since FTP already has this functionality , there 's nothing wrong with using it .
But that 's a far cry from saying that this is really the job of a transport protocol or that it was really a good design decision to put it there .
That 's right .
The fact that FTP does it is not an argument that it is the best place to do it .
The fact that FTP involves a server that knows about the file system it reads and writes files to , and a client that knows about the file system IT reads and writes files to , is why it is the best place to take care of the conversion .
It is stupid for a program designed to transport a certain kind of file from one OS to another to simply ignore the fact that that certain kind of file needs to be converted for use .
If you do n't want FTP converting things for you automatically , use BIN mode for all your transfers .
I like the fact that I do n't have to worry about what format the stupid text file is in when I move data around automatically .
Really , FTP worrying about this would be a little like Ethernet trying to detect and transcode streaming video .
Patently absurd .
Ethernet is a hardware layer ; FTP is a software layer .
Ethernet has no concept of what it carries ; FTP KNOWS the file structures because it has to .
... I 'd be told that this functionality does not belong at the link layer and that it 's the application 's problem to worry about this .
That 's right .
And FTP is an APPLICATION .
It is THE ONLY application that knows what the source and destination formats are and how to convert them .
That makes FTP the right place to deal with the conversion .
We are n't just talking about CRLF/NL differences , remember ?
The crux of the disagreement is this : some people think that their convenience overrides what would otherwise be recognized as a poor or at least questionable design decision .
No , the crux is that some people are very limited in the experiences they have with data management and transport and assume that everything they talk to is just like what they use at home , and thus no conversions are necessary .
In those few cases when they are necessary , they assume that their usage of the computer ( download a few files ) is what everyone else is doing , and that it is simpler to use a standalone converter to convert the " few files " .
This leads them to THINK that the FTP design decision was poor , when it really is their understanding of the scope of the problem that is poor .
Other people think that the soundness of a design decision should come first and convenience should be a secondary concern , particularly when there are other , quite viable options for handling the problem .
The other options are not that viable when you are dealing with large volumes of data automatically .
The design decision is sound because it is both doing the work where it can be done automatically AND makes life a lot more convenient even for people who have no idea that there would otherwise be a problem .
It is patently stupid to force people to make an additional step to convert a file from an " oddball OS " structure into something usable when the transport software can do it for them .
If you want an analogy , it is no different than an email program that forces</tokentext>
<sentencetext>Sorry, but if that applied to me, I would say "hey, the vast majority of people don't need to do this, so this is (relatively) uniquely my problem and I should find my own solution, such as conversion programs".
The problem is that the vast majority of people wouldn't know when to look for the problem and wouldn't know how to solve it when it appeared.
The BEST place to solve this kind of problem is where both ends know it exists and how to solve it automatically.
E.g., in FTP, where the server knows about the host's file system oddities and the client knows the client's.
I didn't ask FTP to deal with this, it was dealing with this a long time before I used it.
Apparently it solved a LOT of people's problems, not just mine.
Now, since FTP already has this functionality, there's nothing wrong with using it.
But that's a far cry from saying that this is really the job of a transport protocol or that it was really a good design decision to put it there.
That's right.
The fact that FTP does it is not an argument that it is the best place to do it.
The fact that FTP involves a server that knows about the file system it reads and writes files to, and a client that knows about the file system IT reads and writes files to, is why it is the best place to take care of the conversion.
It is stupid for a program designed to transport a certain kind of file from one OS to another to simply ignore the fact that that certain kind of file needs to be converted for use.
If you don't want FTP converting things for you automatically, use BIN mode for all your transfers.
I like the fact that I don't have to worry about what format the stupid text file is in when I move data around automatically.
Really, FTP worrying about this would be a little like Ethernet trying to detect and transcode streaming video.
Patently absurd.
Ethernet is a hardware layer; FTP is a software layer.
Ethernet has no concept of what it carries; FTP KNOWS the file structures because it has to.
... I'd be told that this functionality does not belong at the link layer and that it's the application's problem to worry about this.
That's right.
And FTP is an APPLICATION.
It is THE ONLY application that knows what the source and destination formats are and how to convert them.
That makes FTP the right place to deal with the conversion.
We aren't just talking about CRLF/NL differences, remember?
The crux of the disagreement is this: some people think that their convenience overrides what would otherwise be recognized as a poor or at least questionable design decision.
No, the crux is that some people are very limited in the experiences they have with data management and transport and assume that everything they talk to is just like what they use at home, and thus no conversions are necessary.
In those few cases when they are necessary, they assume that their usage of the computer (download a few files) is what everyone else is doing, and that it is simpler to use a standalone converter to convert the "few files".
This leads them to THINK that the FTP design decision was poor, when it really is their understanding of the scope of the problem that is poor.
Other people think that the soundness of a design decision should come first and convenience should be a secondary concern, particularly when there are other, quite viable options for handling the problem.
The other options are not that viable when you are dealing with large volumes of data automatically.
The design decision is sound because it is both doing the work where it can be done automatically AND makes life a lot more convenient even for people who have no idea that there would otherwise be a problem.
It is patently stupid to force people to make an additional step to convert a file from an "oddball OS" structure into something usable when the transport software can do it for them.
If you want an analogy, it is no different than an email program that forces</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542437</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531891</id>
	<title>Microsoft Message Queuing</title>
	<author>ckhorne</author>
	<datestamp>1246387980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I worked on a project that had similar deployment requirements, and we could that using Microsoft Message Queuing (MSMQ) as the transport mechanism took care of all these issues.</p><p>MSMQ itself only provides the transport mechanism, and there's no front end interface to send files- you'd have to code something up. However, it's the best "guaranteed delivery" system that I've seen on the Microsoft platform. Persistent across reboots, security controlled, FIFO queuing, very robust.</p><p>You may not be looking to code something up, but if you are, have a look at that.</p></htmltext>
<tokenext>I worked on a project that had similar deployment requirements , and we could that using Microsoft Message Queuing ( MSMQ ) as the transport mechanism took care of all these issues.MSMQ itself only provides the transport mechanism , and there 's no front end interface to send files- you 'd have to code something up .
However , it 's the best " guaranteed delivery " system that I 've seen on the Microsoft platform .
Persistent across reboots , security controlled , FIFO queuing , very robust.You may not be looking to code something up , but if you are , have a look at that .</tokentext>
<sentencetext>I worked on a project that had similar deployment requirements, and we could that using Microsoft Message Queuing (MSMQ) as the transport mechanism took care of all these issues.MSMQ itself only provides the transport mechanism, and there's no front end interface to send files- you'd have to code something up.
However, it's the best "guaranteed delivery" system that I've seen on the Microsoft platform.
Persistent across reboots, security controlled, FIFO queuing, very robust.You may not be looking to code something up, but if you are, have a look at that.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531821</id>
	<title>Re:Correct me if I'm wrong...</title>
	<author>Anonymous</author>
	<datestamp>1246387740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>TCP only makes sure that a stream of packets will be sent from one host to another without error, it does not know how many total packets are involved in a transfer. It is up to the application that uses TCP to make sure that all of the packets have arrived. For example, if the connection gets cut during a transfer, some applications will leave a partial file and in some cases will print an obscure error somewhere that it may not even be seen. IMHO, any file transfer program that is worth anything at all will transfer the file to a temporary location until all of the file has been received, then rename it to the target name when it has been verified by some sort of a checksum. IE rsync.</p></htmltext>
<tokenext>TCP only makes sure that a stream of packets will be sent from one host to another without error , it does not know how many total packets are involved in a transfer .
It is up to the application that uses TCP to make sure that all of the packets have arrived .
For example , if the connection gets cut during a transfer , some applications will leave a partial file and in some cases will print an obscure error somewhere that it may not even be seen .
IMHO , any file transfer program that is worth anything at all will transfer the file to a temporary location until all of the file has been received , then rename it to the target name when it has been verified by some sort of a checksum .
IE rsync .</tokentext>
<sentencetext>TCP only makes sure that a stream of packets will be sent from one host to another without error, it does not know how many total packets are involved in a transfer.
It is up to the application that uses TCP to make sure that all of the packets have arrived.
For example, if the connection gets cut during a transfer, some applications will leave a partial file and in some cases will print an obscure error somewhere that it may not even be seen.
IMHO, any file transfer program that is worth anything at all will transfer the file to a temporary location until all of the file has been received, then rename it to the target name when it has been verified by some sort of a checksum.
IE rsync.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530895</id>
	<title>the dumb simple solution</title>
	<author>zx-15</author>
	<datestamp>1246384920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>How about creating SHA1 checksum and then transferring data using netcat? You could split files in pieces then run them though sha1 and finally send over netcat using udp and retransmit at will. Or if files don't change too much you could try rsync.</p><p>This is all unix-centric solutions, so you'd have to install cygwin, unless there exists a python library that does all that.</p></htmltext>
<tokenext>How about creating SHA1 checksum and then transferring data using netcat ?
You could split files in pieces then run them though sha1 and finally send over netcat using udp and retransmit at will .
Or if files do n't change too much you could try rsync.This is all unix-centric solutions , so you 'd have to install cygwin , unless there exists a python library that does all that .</tokentext>
<sentencetext>How about creating SHA1 checksum and then transferring data using netcat?
You could split files in pieces then run them though sha1 and finally send over netcat using udp and retransmit at will.
Or if files don't change too much you could try rsync.This is all unix-centric solutions, so you'd have to install cygwin, unless there exists a python library that does all that.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532825</id>
	<title>Cygwin + lpd</title>
	<author>Anonymous</author>
	<datestamp>1246391280000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>Set up a BSD lpd queue under Cygwin, something like:</p><p>sendit:lp=/spool/null:sd=/spool:if=/spool/sendit.sh:sf:sh:mx#0:</p><p>Have the sendit.sh script do whatever it is you want with the file.  To send a file:  lpr -Psendit <i>filename</i> </p><p>Configuration of the network queue left as an exercise for the student.  (Hint - queue pathnames locally.)</p></htmltext>
<tokenext>Set up a BSD lpd queue under Cygwin , something like : sendit : lp = /spool/null : sd = /spool : if = /spool/sendit.sh : sf : sh : mx # 0 : Have the sendit.sh script do whatever it is you want with the file .
To send a file : lpr -Psendit filename Configuration of the network queue left as an exercise for the student .
( Hint - queue pathnames locally .
)</tokentext>
<sentencetext>Set up a BSD lpd queue under Cygwin, something like:sendit:lp=/spool/null:sd=/spool:if=/spool/sendit.sh:sf:sh:mx#0:Have the sendit.sh script do whatever it is you want with the file.
To send a file:  lpr -Psendit filename Configuration of the network queue left as an exercise for the student.
(Hint - queue pathnames locally.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540089</id>
	<title>Re:TCP?</title>
	<author>TheTurtlesMoves</author>
	<datestamp>1246445280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>IPv6 fixes this issue. If they can use IPv6 on this link, problem solved.</htmltext>
<tokenext>IPv6 fixes this issue .
If they can use IPv6 on this link , problem solved .</tokentext>
<sentencetext>IPv6 fixes this issue.
If they can use IPv6 on this link, problem solved.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531775</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530811</id>
	<title>Re:rsync</title>
	<author>Jestrzcap</author>
	<datestamp>1246384740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No mod points, but this is the answer to your question.</p></htmltext>
<tokenext>No mod points , but this is the answer to your question .</tokentext>
<sentencetext>No mod points, but this is the answer to your question.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530399</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533977</id>
	<title>Re:You're kidding, aren't you??</title>
	<author>eap</author>
	<datestamp>1246353000000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I think you missed the part about the government being involved</p></htmltext>
<tokenext>I think you missed the part about the government being involved</tokentext>
<sentencetext>I think you missed the part about the government being involved</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377</id>
	<title>Guaranteed?</title>
	<author>GravityStar</author>
	<datestamp>1246383660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"Guaranteed<nobr> <wbr></nobr>... mission critical files<nobr> <wbr></nobr>... microwave connection<nobr> <wbr></nobr>... government-run<nobr> <wbr></nobr>... very dodgy internal network"</p><p>A transactional store and source integrity verification at the destination point. Or something in between that and what you have now, depending on your requirements. I don't know of a tool that does that out of the box though.</p></htmltext>
<tokenext>" Guaranteed ... mission critical files ... microwave connection ... government-run ... very dodgy internal network " A transactional store and source integrity verification at the destination point .
Or something in between that and what you have now , depending on your requirements .
I do n't know of a tool that does that out of the box though .</tokentext>
<sentencetext>"Guaranteed ... mission critical files ... microwave connection ... government-run ... very dodgy internal network"A transactional store and source integrity verification at the destination point.
Or something in between that and what you have now, depending on your requirements.
I don't know of a tool that does that out of the box though.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535223</id>
	<title>Re:UDP.</title>
	<author>Nefarious Wheel</author>
	<datestamp>1246358700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'd go for the secret, hollowed-out coin myself.</htmltext>
<tokenext>I 'd go for the secret , hollowed-out coin myself .</tokentext>
<sentencetext>I'd go for the secret, hollowed-out coin myself.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540423</id>
	<title>Get a better editor: Notepad++</title>
	<author>tepples</author>
	<datestamp>1246450320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Try opening a newlined file with notepad, for example.</p></div><p>
Gedit on my Ubuntu laptop saves with LF newlines, and Windows Notepad can't read them because it expects CRLF newlines. But I <a href="http://notepad-plus.sourceforge.net/uk/site.htm" title="sourceforge.net">add one to Notepad</a> [sourceforge.net] and all is well. In fact, pretty much every text editor <em>but</em> Windows Notepad can handle the differences between UNIX and Windows.
</p><p>
As for VMS, how much VMS is used in world-facing applications as of June 2009? Even HP, the owner of copyright in VMS after having bought Digital's parent company, uses HP-UX, Linux, or Windows Server on <a href="http://searchdns.netcraft.com/?position=limited&amp;host=.hp.com" title="netcraft.com">its popular public websites</a> [netcraft.com]. Even <a href="http://h71000.www7.hp.com/" title="hp.com">HP's site about VMS</a> [hp.com] was found to <a href="http://toolbar.netcraft.com/site\_report?url=http://h71000.www7.hp.com" title="netcraft.com">use HP-UX</a> [netcraft.com]. Netcraft confirms it: VMS is dead.
</p><p>
And if FTP translates oddball operating systems' conventions for <tt>text/plain</tt> files, why doesn't it do so for image files (.ppm vs.<nobr> <wbr></nobr>.bmp), audio files (.au vs.<nobr> <wbr></nobr>.wav), or other MIME types?
</p></div>
	</htmltext>
<tokenext>Try opening a newlined file with notepad , for example .
Gedit on my Ubuntu laptop saves with LF newlines , and Windows Notepad ca n't read them because it expects CRLF newlines .
But I add one to Notepad [ sourceforge.net ] and all is well .
In fact , pretty much every text editor but Windows Notepad can handle the differences between UNIX and Windows .
As for VMS , how much VMS is used in world-facing applications as of June 2009 ?
Even HP , the owner of copyright in VMS after having bought Digital 's parent company , uses HP-UX , Linux , or Windows Server on its popular public websites [ netcraft.com ] .
Even HP 's site about VMS [ hp.com ] was found to use HP-UX [ netcraft.com ] .
Netcraft confirms it : VMS is dead .
And if FTP translates oddball operating systems ' conventions for text/plain files , why does n't it do so for image files ( .ppm vs. .bmp ) , audio files ( .au vs. .wav ) , or other MIME types ?</tokentext>
<sentencetext>Try opening a newlined file with notepad, for example.
Gedit on my Ubuntu laptop saves with LF newlines, and Windows Notepad can't read them because it expects CRLF newlines.
But I add one to Notepad [sourceforge.net] and all is well.
In fact, pretty much every text editor but Windows Notepad can handle the differences between UNIX and Windows.
As for VMS, how much VMS is used in world-facing applications as of June 2009?
Even HP, the owner of copyright in VMS after having bought Digital's parent company, uses HP-UX, Linux, or Windows Server on its popular public websites [netcraft.com].
Even HP's site about VMS [hp.com] was found to use HP-UX [netcraft.com].
Netcraft confirms it: VMS is dead.
And if FTP translates oddball operating systems' conventions for text/plain files, why doesn't it do so for image files (.ppm vs. .bmp), audio files (.au vs. .wav), or other MIME types?

	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534393</id>
	<title>Microsoft Distributed File System Replication</title>
	<author>Anonymous</author>
	<datestamp>1246354620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Look into Microsoft DFSR. If the servers are 2003 you just need to install the R2 update and configure it. Setup a source folder on your server and a target folder on the destination server. Excellent on a low bandwidth connection.</p></htmltext>
<tokenext>Look into Microsoft DFSR .
If the servers are 2003 you just need to install the R2 update and configure it .
Setup a source folder on your server and a target folder on the destination server .
Excellent on a low bandwidth connection .</tokentext>
<sentencetext>Look into Microsoft DFSR.
If the servers are 2003 you just need to install the R2 update and configure it.
Setup a source folder on your server and a target folder on the destination server.
Excellent on a low bandwidth connection.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531525</id>
	<title>Re:Line endings!</title>
	<author>Anonymous</author>
	<datestamp>1246386720000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>its crlf not lf cr.</p></htmltext>
<tokenext>its crlf not lf cr .</tokentext>
<sentencetext>its crlf not lf cr.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538575</id>
	<title>DECnet</title>
	<author>Anonymous</author>
	<datestamp>1246383000000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'd say <a href="http://thedailywtf.com/Articles/A-Systematic-Approach.aspx" title="thedailywtf.com" rel="nofollow">DECnet</a> [thedailywtf.com].</p></htmltext>
<tokenext>I 'd say DECnet [ thedailywtf.com ] .</tokentext>
<sentencetext>I'd say DECnet [thedailywtf.com].</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534715</id>
	<title>Grr</title>
	<author>Anonymous</author>
	<datestamp>1246355940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The OP is confused.</p><p>He already has a reliable file transfer program (FTP) and he doesn't need anything new.</p><p>How did this question get past the gate to be published to the site? Doesn't anyone check the questions before they are put up?</p><p>The OP is either not switching to binary transfer or the source file changed during the copy.</p></htmltext>
<tokenext>The OP is confused.He already has a reliable file transfer program ( FTP ) and he does n't need anything new.How did this question get past the gate to be published to the site ?
Does n't anyone check the questions before they are put up ? The OP is either not switching to binary transfer or the source file changed during the copy .</tokentext>
<sentencetext>The OP is confused.He already has a reliable file transfer program (FTP) and he doesn't need anything new.How did this question get past the gate to be published to the site?
Doesn't anyone check the questions before they are put up?The OP is either not switching to binary transfer or the source file changed during the copy.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28546045</id>
	<title>SCTP</title>
	<author>AF\_Cheddar\_Head</author>
	<datestamp>1246474860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I recently worked on a government program that had some of the same requirements that you describe. Lockheed-Martin proposed that they create a custom protocol to do this at the cost of about a zillon dollars. Some research turned up SCTP "http://en.wikipedia.org/wiki/Stream\_Control\_Transmission\_Protocol" which is now available in Windows. We were using an implementation for Solaris.</p></htmltext>
<tokenext>I recently worked on a government program that had some of the same requirements that you describe .
Lockheed-Martin proposed that they create a custom protocol to do this at the cost of about a zillon dollars .
Some research turned up SCTP " http : //en.wikipedia.org/wiki/Stream \ _Control \ _Transmission \ _Protocol " which is now available in Windows .
We were using an implementation for Solaris .</tokentext>
<sentencetext>I recently worked on a government program that had some of the same requirements that you describe.
Lockheed-Martin proposed that they create a custom protocol to do this at the cost of about a zillon dollars.
Some research turned up SCTP "http://en.wikipedia.org/wiki/Stream\_Control\_Transmission\_Protocol" which is now available in Windows.
We were using an implementation for Solaris.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535233</id>
	<title>Break the problem down</title>
	<author>cheros</author>
	<datestamp>1246358760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You raise questions on various levels, so let me traverse the stack in reverse order.</p><p>Link: just how reliable is it?  I assume quality is unpredictable and varies (for instance during mobile and in-theatre deployment), which suggests you need to check for transmission errors in pretty small windows and force a error retransmit ASAP (if you have that capability on your specific type of link).</p><p>Protocol: I won't question using TCP/IP, but I would suggest you may want to ensure you tune the stack to small window sizes, and use UDP as that appears to match your transmission quality.  <a href="http://en.wikipedia.org/wiki/Mobile\_ad-hoc\_network" title="wikipedia.org">MANET</a> [wikipedia.org] could help as well as that's made for mobile use, but I don't really know anything about it - it just may be an option worth checking.</p><p>FTP and TX security: I'm not sure of how sensitive this data is, but a microwave link does have stray signal issues, and FTP transmits UID and password more or less in cleartext.  IMHO not quite desirable, but it depends what you do.  In addition, FTP defaults in Windows to ASCII mode which makes a mess of data that is not of Windows origin or is binary.  You MUST set to "binary" mode first before you start transmission, which others have already mentioned.  In addition, do some tests with checksummed data so when you find differences you can work out if it's your own interpretation or a real problem.</p><p>Personally, I'd grab the <a href="http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html" title="greenend.org.uk">PuTTY</a> [greenend.org.uk] set and run a SSH session.  You can find a server at <a href="http://www.freesshd.com/" title="freesshd.com">FreeSSH</a> [freesshd.com].  Also brutally easy to automate - I expect you're not that much in need of employment that you must generate your own opportunities to watch paint dry<nobr> <wbr></nobr>:-).</p><p>Good luck...</p></htmltext>
<tokenext>You raise questions on various levels , so let me traverse the stack in reverse order.Link : just how reliable is it ?
I assume quality is unpredictable and varies ( for instance during mobile and in-theatre deployment ) , which suggests you need to check for transmission errors in pretty small windows and force a error retransmit ASAP ( if you have that capability on your specific type of link ) .Protocol : I wo n't question using TCP/IP , but I would suggest you may want to ensure you tune the stack to small window sizes , and use UDP as that appears to match your transmission quality .
MANET [ wikipedia.org ] could help as well as that 's made for mobile use , but I do n't really know anything about it - it just may be an option worth checking.FTP and TX security : I 'm not sure of how sensitive this data is , but a microwave link does have stray signal issues , and FTP transmits UID and password more or less in cleartext .
IMHO not quite desirable , but it depends what you do .
In addition , FTP defaults in Windows to ASCII mode which makes a mess of data that is not of Windows origin or is binary .
You MUST set to " binary " mode first before you start transmission , which others have already mentioned .
In addition , do some tests with checksummed data so when you find differences you can work out if it 's your own interpretation or a real problem.Personally , I 'd grab the PuTTY [ greenend.org.uk ] set and run a SSH session .
You can find a server at FreeSSH [ freesshd.com ] .
Also brutally easy to automate - I expect you 're not that much in need of employment that you must generate your own opportunities to watch paint dry : - ) .Good luck.. .</tokentext>
<sentencetext>You raise questions on various levels, so let me traverse the stack in reverse order.Link: just how reliable is it?
I assume quality is unpredictable and varies (for instance during mobile and in-theatre deployment), which suggests you need to check for transmission errors in pretty small windows and force a error retransmit ASAP (if you have that capability on your specific type of link).Protocol: I won't question using TCP/IP, but I would suggest you may want to ensure you tune the stack to small window sizes, and use UDP as that appears to match your transmission quality.
MANET [wikipedia.org] could help as well as that's made for mobile use, but I don't really know anything about it - it just may be an option worth checking.FTP and TX security: I'm not sure of how sensitive this data is, but a microwave link does have stray signal issues, and FTP transmits UID and password more or less in cleartext.
IMHO not quite desirable, but it depends what you do.
In addition, FTP defaults in Windows to ASCII mode which makes a mess of data that is not of Windows origin or is binary.
You MUST set to "binary" mode first before you start transmission, which others have already mentioned.
In addition, do some tests with checksummed data so when you find differences you can work out if it's your own interpretation or a real problem.Personally, I'd grab the PuTTY [greenend.org.uk] set and run a SSH session.
You can find a server at FreeSSH [freesshd.com].
Also brutally easy to automate - I expect you're not that much in need of employment that you must generate your own opportunities to watch paint dry :-).Good luck...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531149</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246385640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>TCP efforts don't fail.  At the IP layer, packets are even checksumed.</p><p>It's FTP client and server software that's unreliable or at issue.<br>Possibly a broken server or client application.</p><p>Possibly a failed attempt at download resume after a file transfer had failed.</p><p>Maybe a disagreement between client and server about resume,  or inappropriate use of 'text' transfers for binary data.</p></htmltext>
<tokenext>TCP efforts do n't fail .
At the IP layer , packets are even checksumed.It 's FTP client and server software that 's unreliable or at issue.Possibly a broken server or client application.Possibly a failed attempt at download resume after a file transfer had failed.Maybe a disagreement between client and server about resume , or inappropriate use of 'text ' transfers for binary data .</tokentext>
<sentencetext>TCP efforts don't fail.
At the IP layer, packets are even checksumed.It's FTP client and server software that's unreliable or at issue.Possibly a broken server or client application.Possibly a failed attempt at download resume after a file transfer had failed.Maybe a disagreement between client and server about resume,  or inappropriate use of 'text' transfers for binary data.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531903</id>
	<title>Been there, done that</title>
	<author>ubersoldat2k7</author>
	<datestamp>1246387980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This same problem happened to us when I was doing "service". Let's just say that something had a computer with an access database, and the mdb had to be sent over a microwave connection to something else (that also had a computer) which took mdb files from many somethings and did some other things.
Well, anyway, at first they we're using FTP, but I got to script a solution that zipped the file over several small ones (50MB each) then sent them over SCP, made a checksum on each file and then rebuilt the mdb file.</htmltext>
<tokenext>This same problem happened to us when I was doing " service " .
Let 's just say that something had a computer with an access database , and the mdb had to be sent over a microwave connection to something else ( that also had a computer ) which took mdb files from many somethings and did some other things .
Well , anyway , at first they we 're using FTP , but I got to script a solution that zipped the file over several small ones ( 50MB each ) then sent them over SCP , made a checksum on each file and then rebuilt the mdb file .</tokentext>
<sentencetext>This same problem happened to us when I was doing "service".
Let's just say that something had a computer with an access database, and the mdb had to be sent over a microwave connection to something else (that also had a computer) which took mdb files from many somethings and did some other things.
Well, anyway, at first they we're using FTP, but I got to script a solution that zipped the file over several small ones (50MB each) then sent them over SCP, made a checksum on each file and then rebuilt the mdb file.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539341</id>
	<title>ZModem</title>
	<author>burisch\_research</author>
	<datestamp>1246478640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Whatever happened to ZModem? It's an amazingly resilient protocol that was used to great effect to transfer files over virtually any phone line, no matter how noisy. It accomplished this by an adaptive algorithm, whereby the block transfer size was either doubled or halved after every few blocks, depending on whether the previous blocks got through the line ok. Where's the equivalent in the modern internet world?? There are millions of people with dodgy or unreliable internet connections -- they would benefit from clients / servers that implemented a modern equivalent.</htmltext>
<tokenext>Whatever happened to ZModem ?
It 's an amazingly resilient protocol that was used to great effect to transfer files over virtually any phone line , no matter how noisy .
It accomplished this by an adaptive algorithm , whereby the block transfer size was either doubled or halved after every few blocks , depending on whether the previous blocks got through the line ok. Where 's the equivalent in the modern internet world ? ?
There are millions of people with dodgy or unreliable internet connections -- they would benefit from clients / servers that implemented a modern equivalent .</tokentext>
<sentencetext>Whatever happened to ZModem?
It's an amazingly resilient protocol that was used to great effect to transfer files over virtually any phone line, no matter how noisy.
It accomplished this by an adaptive algorithm, whereby the block transfer size was either doubled or halved after every few blocks, depending on whether the previous blocks got through the line ok. Where's the equivalent in the modern internet world??
There are millions of people with dodgy or unreliable internet connections -- they would benefit from clients / servers that implemented a modern equivalent.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531045</id>
	<title>XCopy?</title>
	<author>vawarayer</author>
	<datestamp>1246385280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Xcopy<nobr> <wbr></nobr>/v over a network share? using the at command?</htmltext>
<tokenext>Xcopy /v over a network share ?
using the at command ?</tokentext>
<sentencetext>Xcopy /v over a network share?
using the at command?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530239</id>
	<title>Cygwin</title>
	<author>Anonymous</author>
	<datestamp>1246383360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Cygwin + SFTP maybe? Not sure if that performs better. Easy to set up though. May get better grade of service off the network, depending on the rules, of course.</p></htmltext>
<tokenext>Cygwin + SFTP maybe ?
Not sure if that performs better .
Easy to set up though .
May get better grade of service off the network , depending on the rules , of course .</tokentext>
<sentencetext>Cygwin + SFTP maybe?
Not sure if that performs better.
Easy to set up though.
May get better grade of service off the network, depending on the rules, of course.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28546517</id>
	<title>Re:Use .complete files.</title>
	<author>KZigurs</author>
	<datestamp>1246476180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Uhm? If you are allowing for possibility for the remote file to be "bigger", you are allowing for potential data corruption as well even if sizes match. What about three way protocol where there is also a script on the target machine that regulary generates md5 sums (and yes, we STILL can have collision there) for files present and<nobr> <wbr></nobr>.complete is uploaded only if the md5 matches.</p><p>Althou, obviously, this is braindead. I would probably go and just use something like rar with recovery records to make sure that I can detect any issues in one step. Or - just switch network provider, use VNP and then - all of the above together. Assuming that mission critical here indeed means "worth time to attempt to make sure that data gets there ASAP and verifyably* intact or else there will be millions lost."</p><p>*Man in the middle?</p></htmltext>
<tokenext>Uhm ?
If you are allowing for possibility for the remote file to be " bigger " , you are allowing for potential data corruption as well even if sizes match .
What about three way protocol where there is also a script on the target machine that regulary generates md5 sums ( and yes , we STILL can have collision there ) for files present and .complete is uploaded only if the md5 matches.Althou , obviously , this is braindead .
I would probably go and just use something like rar with recovery records to make sure that I can detect any issues in one step .
Or - just switch network provider , use VNP and then - all of the above together .
Assuming that mission critical here indeed means " worth time to attempt to make sure that data gets there ASAP and verifyably * intact or else there will be millions lost .
" * Man in the middle ?</tokentext>
<sentencetext>Uhm?
If you are allowing for possibility for the remote file to be "bigger", you are allowing for potential data corruption as well even if sizes match.
What about three way protocol where there is also a script on the target machine that regulary generates md5 sums (and yes, we STILL can have collision there) for files present and .complete is uploaded only if the md5 matches.Althou, obviously, this is braindead.
I would probably go and just use something like rar with recovery records to make sure that I can detect any issues in one step.
Or - just switch network provider, use VNP and then - all of the above together.
Assuming that mission critical here indeed means "worth time to attempt to make sure that data gets there ASAP and verifyably* intact or else there will be millions lost.
"*Man in the middle?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530867</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534649</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246355700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>FTP wasn't designed just for hobbyists who want a file or two and have the time to deal with file formats by hand. It was designed to move data, and anything that can be automated should be. "Little standalone utilities" are a pain in the ass when trying to automate something, especially when the critical information necessary to know what specific utility to use has been lost, or is completely unknown to the recipient's system. Like VMS fixed length records on Unix or Windows.</p></div><p>More to the point, IMHO, FTP wasn't designed for the modern, nearly homogeneous, internet, which is mostly UNIX with a minority of WinNT. It was designed for a much more diverse internet, where the sort of transitions you discuss were common enough it was not only convenient to handle them, it was <b>necessary</b>. Today, binary mode should be adequate for most professional as well as hobbyist uses, because the predominant systems have minimal differences, and both have utilities to perform the conversions when needed, and so the cleanliness of never mangling data might win over the slight convenience of text transfers for LF/CRLF conversion. But it wasn't designed today.</p></div>
	</htmltext>
<tokenext>FTP was n't designed just for hobbyists who want a file or two and have the time to deal with file formats by hand .
It was designed to move data , and anything that can be automated should be .
" Little standalone utilities " are a pain in the ass when trying to automate something , especially when the critical information necessary to know what specific utility to use has been lost , or is completely unknown to the recipient 's system .
Like VMS fixed length records on Unix or Windows.More to the point , IMHO , FTP was n't designed for the modern , nearly homogeneous , internet , which is mostly UNIX with a minority of WinNT .
It was designed for a much more diverse internet , where the sort of transitions you discuss were common enough it was not only convenient to handle them , it was necessary .
Today , binary mode should be adequate for most professional as well as hobbyist uses , because the predominant systems have minimal differences , and both have utilities to perform the conversions when needed , and so the cleanliness of never mangling data might win over the slight convenience of text transfers for LF/CRLF conversion .
But it was n't designed today .</tokentext>
<sentencetext>FTP wasn't designed just for hobbyists who want a file or two and have the time to deal with file formats by hand.
It was designed to move data, and anything that can be automated should be.
"Little standalone utilities" are a pain in the ass when trying to automate something, especially when the critical information necessary to know what specific utility to use has been lost, or is completely unknown to the recipient's system.
Like VMS fixed length records on Unix or Windows.More to the point, IMHO, FTP wasn't designed for the modern, nearly homogeneous, internet, which is mostly UNIX with a minority of WinNT.
It was designed for a much more diverse internet, where the sort of transitions you discuss were common enough it was not only convenient to handle them, it was necessary.
Today, binary mode should be adequate for most professional as well as hobbyist uses, because the predominant systems have minimal differences, and both have utilities to perform the conversions when needed, and so the cleanliness of never mangling data might win over the slight convenience of text transfers for LF/CRLF conversion.
But it wasn't designed today.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534267</id>
	<title>Re:UDP.</title>
	<author>Anonymous</author>
	<datestamp>1246354200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Another option is Par files, they create files 10\% the size of the originals and if any of the files become corrupted they will detect and repair.</p></htmltext>
<tokenext>Another option is Par files , they create files 10 \ % the size of the originals and if any of the files become corrupted they will detect and repair .</tokentext>
<sentencetext>Another option is Par files, they create files 10\% the size of the originals and if any of the files become corrupted they will detect and repair.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</id>
	<title>Correct me if I'm wrong...</title>
	<author>not already in use</author>
	<datestamp>1246383300000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>Wasn't TCP designed for just this?  Guaranteed transmission?</htmltext>
<tokenext>Was n't TCP designed for just this ?
Guaranteed transmission ?</tokentext>
<sentencetext>Wasn't TCP designed for just this?
Guaranteed transmission?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530595</id>
	<title>Two words:</title>
	<author>jpm242</author>
	<datestamp>1246384260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>DVD burner, FedEx.</p></htmltext>
<tokenext>DVD burner , FedEx .</tokentext>
<sentencetext>DVD burner, FedEx.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539825</id>
	<title>plain-text: !ascii but unencrypted</title>
	<author>jonaskoelker</author>
	<datestamp>1246442220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>SFTP [...] SSL [...] FTP is a plain-text protocol</p></div><p><div class="quote"><p>Wrong. FTP has a binary mode.</p></div><p>When we're talking in crypto-mode---as we are, made evident by the references to SFTP and SLL---the words "plain-text" refer not to ascii vs. base64 vs. bin2hex encoding, but whether the data is encrypted or not.</p><p>AFAIK, FTP doesn't have any provisions for encryption.</p><p>Your point is orthogonal to that, so your "Wrong" is wrong: your parent is not wrong.  Your point is true, however: FTP does have issues with line endings etc.; rule of thumb: use binary for everything and recode newlines on the client side if need be.</p><p><div class="quote"><p>Using SFTP over an already secure network will only slow things down greatly.</p></div><p>Sending data unencrypted through the air is not what I consider "secure".  So, while true, this point is not particularly relevant (I think).</p></div>
	</htmltext>
<tokenext>SFTP [ ... ] SSL [ ... ] FTP is a plain-text protocolWrong .
FTP has a binary mode.When we 're talking in crypto-mode---as we are , made evident by the references to SFTP and SLL---the words " plain-text " refer not to ascii vs. base64 vs. bin2hex encoding , but whether the data is encrypted or not.AFAIK , FTP does n't have any provisions for encryption.Your point is orthogonal to that , so your " Wrong " is wrong : your parent is not wrong .
Your point is true , however : FTP does have issues with line endings etc .
; rule of thumb : use binary for everything and recode newlines on the client side if need be.Using SFTP over an already secure network will only slow things down greatly.Sending data unencrypted through the air is not what I consider " secure " .
So , while true , this point is not particularly relevant ( I think ) .</tokentext>
<sentencetext>SFTP [...] SSL [...] FTP is a plain-text protocolWrong.
FTP has a binary mode.When we're talking in crypto-mode---as we are, made evident by the references to SFTP and SLL---the words "plain-text" refer not to ascii vs. base64 vs. bin2hex encoding, but whether the data is encrypted or not.AFAIK, FTP doesn't have any provisions for encryption.Your point is orthogonal to that, so your "Wrong" is wrong: your parent is not wrong.
Your point is true, however: FTP does have issues with line endings etc.
; rule of thumb: use binary for everything and recode newlines on the client side if need be.Using SFTP over an already secure network will only slow things down greatly.Sending data unencrypted through the air is not what I consider "secure".
So, while true, this point is not particularly relevant (I think).
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28537525</id>
	<title>Torrent</title>
	<author>ill1cit</author>
	<datestamp>1246372920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Bit Torrent protocol would be the simplest .</htmltext>
<tokenext>Bit Torrent protocol would be the simplest .</tokentext>
<sentencetext>Bit Torrent protocol would be the simplest .</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</id>
	<title>Line endings!</title>
	<author>sys.stdout.write</author>
	<datestamp>1246383360000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals</p></div><p>
Twenty bucks says you're converting from Windows line endings (/n/r) to Linux line endings (/n).<br> <br>Use binary mode and you'll be fine.</p></div>
	</htmltext>
<tokenext>they 've been using FTP to upload the files , but many times the copied files are a few kilobytes smaller than the originals Twenty bucks says you 're converting from Windows line endings ( /n/r ) to Linux line endings ( /n ) .
Use binary mode and you 'll be fine .</tokentext>
<sentencetext>they've been using FTP to upload the files, but many times the copied files are a few kilobytes smaller than the originals
Twenty bucks says you're converting from Windows line endings (/n/r) to Linux line endings (/n).
Use binary mode and you'll be fine.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530921</id>
	<title>How about just going to the past?</title>
	<author>loftwyr</author>
	<datestamp>1246384980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Back in the very old days, we had slow modems with noisy lines.  We used thinks like <a href="http://www.omen.com/products.html" title="omen.com">Zmodem</a> [omen.com] and other things to handle this problem.

It might just be the thing that will work now to solve your problem.</htmltext>
<tokenext>Back in the very old days , we had slow modems with noisy lines .
We used thinks like Zmodem [ omen.com ] and other things to handle this problem .
It might just be the thing that will work now to solve your problem .</tokentext>
<sentencetext>Back in the very old days, we had slow modems with noisy lines.
We used thinks like Zmodem [omen.com] and other things to handle this problem.
It might just be the thing that will work now to solve your problem.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531771</id>
	<title>Re:RTFM - set binary mode in FTP</title>
	<author>reg106</author>
	<datestamp>1246387500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Is that Dennis Ritchie, as in Kernighan and Ritchie?  I never heard a name for the law and can't find it after a quick internet search.  If you have any further information I'd appreciate it...</htmltext>
<tokenext>Is that Dennis Ritchie , as in Kernighan and Ritchie ?
I never heard a name for the law and ca n't find it after a quick internet search .
If you have any further information I 'd appreciate it.. .</tokentext>
<sentencetext>Is that Dennis Ritchie, as in Kernighan and Ritchie?
I never heard a name for the law and can't find it after a quick internet search.
If you have any further information I'd appreciate it...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535003</id>
	<title>DTN?</title>
	<author>Anonymous</author>
	<datestamp>1246357500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>http://www.ietf.org/rfc/rfc4838.txt</p></htmltext>
<tokenext>http : //www.ietf.org/rfc/rfc4838.txt</tokentext>
<sentencetext>http://www.ietf.org/rfc/rfc4838.txt</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531293</id>
	<title>PAR2?</title>
	<author>cyberjock1980</author>
	<datestamp>1246386000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Create a small set of PAR2 files.  At the destination compare it.  If it needs repair, then get the associated repair blocks.  This solves 2 problems...</p><p>1.  Don't have to retransmit a corrupted file.  What's the good in knowing it's bad if you'll have to redownload it again.<br>2.  Fixes the errors for minimal bandwidth.  Due to the fact you mentioned the bandwidth limitation, I assume this is a major obstacle to just resending the file again when it's corrupt.</p></htmltext>
<tokenext>Create a small set of PAR2 files .
At the destination compare it .
If it needs repair , then get the associated repair blocks .
This solves 2 problems...1 .
Do n't have to retransmit a corrupted file .
What 's the good in knowing it 's bad if you 'll have to redownload it again.2 .
Fixes the errors for minimal bandwidth .
Due to the fact you mentioned the bandwidth limitation , I assume this is a major obstacle to just resending the file again when it 's corrupt .</tokentext>
<sentencetext>Create a small set of PAR2 files.
At the destination compare it.
If it needs repair, then get the associated repair blocks.
This solves 2 problems...1.
Don't have to retransmit a corrupted file.
What's the good in knowing it's bad if you'll have to redownload it again.2.
Fixes the errors for minimal bandwidth.
Due to the fact you mentioned the bandwidth limitation, I assume this is a major obstacle to just resending the file again when it's corrupt.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28556987</id>
	<title>IBM WebSphere MQ</title>
	<author>Manic Miner</author>
	<datestamp>1246546260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It costs money, but buy the file transfer edition. You get reliable and encrypted data transmission.</p><p>Simple<nobr> <wbr></nobr>:)</p></htmltext>
<tokenext>It costs money , but buy the file transfer edition .
You get reliable and encrypted data transmission.Simple : )</tokentext>
<sentencetext>It costs money, but buy the file transfer edition.
You get reliable and encrypted data transmission.Simple :)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532443</id>
	<title>RCF 1149 - IP over Avian Carrier</title>
	<author>grx0</author>
	<datestamp>1246389900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>because microwave apparently is just as prone to loss.</p><p>http://www.rfc-editor.org/rfc/rfc1149.txt</p></htmltext>
<tokenext>because microwave apparently is just as prone to loss.http : //www.rfc-editor.org/rfc/rfc1149.txt</tokentext>
<sentencetext>because microwave apparently is just as prone to loss.http://www.rfc-editor.org/rfc/rfc1149.txt</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533485</id>
	<title>SSHFS</title>
	<author>cenc</author>
	<datestamp>1246394220000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I use sshfs file mounts for all office document file sharing and such, not just one time transfers. SSH encryption security, with the ability to open and edit files over the network. No goofing around with samba or windows file sharing. Regardless, some sort of ssh or sftp at least.</p><p>Not sure about getting it to work on windows, but there should be some options.</p></htmltext>
<tokenext>I use sshfs file mounts for all office document file sharing and such , not just one time transfers .
SSH encryption security , with the ability to open and edit files over the network .
No goofing around with samba or windows file sharing .
Regardless , some sort of ssh or sftp at least.Not sure about getting it to work on windows , but there should be some options .</tokentext>
<sentencetext>I use sshfs file mounts for all office document file sharing and such, not just one time transfers.
SSH encryption security, with the ability to open and edit files over the network.
No goofing around with samba or windows file sharing.
Regardless, some sort of ssh or sftp at least.Not sure about getting it to work on windows, but there should be some options.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28541853</id>
	<title>TeraCopy</title>
	<author>InvisiBill</author>
	<datestamp>1246461180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm assuming you want something scriptable, but as a regular GUI replacement for Windows' file copy stuff, TeraCopy (<a href="http://www.codesector.com/teracopy.php" title="codesector.com">http://www.codesector.com/teracopy.php</a> [codesector.com]) is quite nice.  It's sort of like a GUI version of Robocopy.</p><p>FYI, the 32-bit version integrates perfectly with the Windows shell, but the 64-bit version's integration was a complete pile the last time I tried it (a while ago).  It didn't work automatically after the installation, and even the manual integration instructions didn't get it working.  TeraCopy is much less useful when you specifically have to open the app and select the source and destination to start the copy.</p></htmltext>
<tokenext>I 'm assuming you want something scriptable , but as a regular GUI replacement for Windows ' file copy stuff , TeraCopy ( http : //www.codesector.com/teracopy.php [ codesector.com ] ) is quite nice .
It 's sort of like a GUI version of Robocopy.FYI , the 32-bit version integrates perfectly with the Windows shell , but the 64-bit version 's integration was a complete pile the last time I tried it ( a while ago ) .
It did n't work automatically after the installation , and even the manual integration instructions did n't get it working .
TeraCopy is much less useful when you specifically have to open the app and select the source and destination to start the copy .</tokentext>
<sentencetext>I'm assuming you want something scriptable, but as a regular GUI replacement for Windows' file copy stuff, TeraCopy (http://www.codesector.com/teracopy.php [codesector.com]) is quite nice.
It's sort of like a GUI version of Robocopy.FYI, the 32-bit version integrates perfectly with the Windows shell, but the 64-bit version's integration was a complete pile the last time I tried it (a while ago).
It didn't work automatically after the installation, and even the manual integration instructions didn't get it working.
TeraCopy is much less useful when you specifically have to open the app and select the source and destination to start the copy.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534405</id>
	<title>Re:TCP?</title>
	<author>jgrahn</author>
	<datestamp>1246354680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>On the other hand, if you really want a "guaranteed delivery" with formal acknowledgment and validation, try using a secured protocol like SSH or SFTP or a messaging system like JMS with a handshaking architecture around it. There are plenty of Open Source architectures you can build around (xBus for example), but I don't know of any ready-built executables. Commercially, vendors like IBM (MQ) and Tibco have products that deal with the messaging at a similar level.</p></div></blockquote><p>
I can't help reading that and thinking "why on earth would anyone want to go build an IBM MQSeries messaging, uh, architecture when (as you point out) you can just use something like SFTP or rsync-over-ssh which everyone uses,
works, and is free as the air I breathe?"</p></div>
	</htmltext>
<tokenext>On the other hand , if you really want a " guaranteed delivery " with formal acknowledgment and validation , try using a secured protocol like SSH or SFTP or a messaging system like JMS with a handshaking architecture around it .
There are plenty of Open Source architectures you can build around ( xBus for example ) , but I do n't know of any ready-built executables .
Commercially , vendors like IBM ( MQ ) and Tibco have products that deal with the messaging at a similar level .
I ca n't help reading that and thinking " why on earth would anyone want to go build an IBM MQSeries messaging , uh , architecture when ( as you point out ) you can just use something like SFTP or rsync-over-ssh which everyone uses , works , and is free as the air I breathe ?
"</tokentext>
<sentencetext>On the other hand, if you really want a "guaranteed delivery" with formal acknowledgment and validation, try using a secured protocol like SSH or SFTP or a messaging system like JMS with a handshaking architecture around it.
There are plenty of Open Source architectures you can build around (xBus for example), but I don't know of any ready-built executables.
Commercially, vendors like IBM (MQ) and Tibco have products that deal with the messaging at a similar level.
I can't help reading that and thinking "why on earth would anyone want to go build an IBM MQSeries messaging, uh, architecture when (as you point out) you can just use something like SFTP or rsync-over-ssh which everyone uses,
works, and is free as the air I breathe?
"
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531239</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530335</id>
	<title>Sneakernet</title>
	<author>Anonymous</author>
	<datestamp>1246383540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Probably tape drives, or hard drives if you prefer.  Encrypt with a shared key.  I think microwave is LOS already, so your distances can't be that large.   It would certainly solve your "flaky" bandwidth and security considerations.  You would "packetize" the data, eg:  tapes are brought over in serial succession;  if a tape went missing, you delete the key that encrypted it's contents and request a resend of the contents of that tape.  That verifies it's receipt.</p><p>Not sexy, but it's probably the best solution.  Since you're a government contractor,  I'll now insult you to suggest that you need a project for which you can charge a lot more money, like a carrier pigeon training program, including pigeon consultants, a pigeon breeding program, and a pigeon habitat designer.  But that's what you get for asking Slashdot to do your job for you, especially one with an obvious, non-sexy, non-technical solution.</p></htmltext>
<tokenext>Probably tape drives , or hard drives if you prefer .
Encrypt with a shared key .
I think microwave is LOS already , so your distances ca n't be that large .
It would certainly solve your " flaky " bandwidth and security considerations .
You would " packetize " the data , eg : tapes are brought over in serial succession ; if a tape went missing , you delete the key that encrypted it 's contents and request a resend of the contents of that tape .
That verifies it 's receipt.Not sexy , but it 's probably the best solution .
Since you 're a government contractor , I 'll now insult you to suggest that you need a project for which you can charge a lot more money , like a carrier pigeon training program , including pigeon consultants , a pigeon breeding program , and a pigeon habitat designer .
But that 's what you get for asking Slashdot to do your job for you , especially one with an obvious , non-sexy , non-technical solution .</tokentext>
<sentencetext>Probably tape drives, or hard drives if you prefer.
Encrypt with a shared key.
I think microwave is LOS already, so your distances can't be that large.
It would certainly solve your "flaky" bandwidth and security considerations.
You would "packetize" the data, eg:  tapes are brought over in serial succession;  if a tape went missing, you delete the key that encrypted it's contents and request a resend of the contents of that tape.
That verifies it's receipt.Not sexy, but it's probably the best solution.
Since you're a government contractor,  I'll now insult you to suggest that you need a project for which you can charge a lot more money, like a carrier pigeon training program, including pigeon consultants, a pigeon breeding program, and a pigeon habitat designer.
But that's what you get for asking Slashdot to do your job for you, especially one with an obvious, non-sexy, non-technical solution.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532467</id>
	<title>Re:Correct me if I'm wrong...</title>
	<author>Facegarden</author>
	<datestamp>1246389960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Wasn't TCP designed for just this?  Guaranteed transmission?</p></div><p>I'm being extremely pedantic, but there is no such thing as guaranteed transmission. The best protocol in the world won't help you if the connection breaks!<br>I'll go back into my hole now....<br>-Taylor</p></div>
	</htmltext>
<tokenext>Was n't TCP designed for just this ?
Guaranteed transmission ? I 'm being extremely pedantic , but there is no such thing as guaranteed transmission .
The best protocol in the world wo n't help you if the connection breaks ! I 'll go back into my hole now....-Taylor</tokentext>
<sentencetext>Wasn't TCP designed for just this?
Guaranteed transmission?I'm being extremely pedantic, but there is no such thing as guaranteed transmission.
The best protocol in the world won't help you if the connection breaks!I'll go back into my hole now....-Taylor
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532209</id>
	<title>Re:Jesus protocol</title>
	<author>blackjackshellac</author>
	<datestamp>1246389060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Unfortunately the Jesus Protocol is replete with transmission errors.</p><p>&lt;rimshot/&gt;</p></htmltext>
<tokenext>Unfortunately the Jesus Protocol is replete with transmission errors .</tokentext>
<sentencetext>Unfortunately the Jesus Protocol is replete with transmission errors.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530163</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539373</id>
	<title>Re:Guaranteed?</title>
	<author>Anonymous</author>
	<datestamp>1246478940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Not only that, but then the poster says the files were a few kilobytes shorter.... I mean c'mon you would at least think he would have investigated and found out what was going on. From the post it almost sounds like the poster and everyone involved are relatively computer illiterate except for basic computer use. And what does he mean 'better' than a windows file system copy? I think he needs to get someone who has a clue instead of getting this nonsense posted to the front page of slashdot...</p></htmltext>
<tokenext>Not only that , but then the poster says the files were a few kilobytes shorter.... I mean c'mon you would at least think he would have investigated and found out what was going on .
From the post it almost sounds like the poster and everyone involved are relatively computer illiterate except for basic computer use .
And what does he mean 'better ' than a windows file system copy ?
I think he needs to get someone who has a clue instead of getting this nonsense posted to the front page of slashdot.. .</tokentext>
<sentencetext>Not only that, but then the poster says the files were a few kilobytes shorter.... I mean c'mon you would at least think he would have investigated and found out what was going on.
From the post it almost sounds like the poster and everyone involved are relatively computer illiterate except for basic computer use.
And what does he mean 'better' than a windows file system copy?
I think he needs to get someone who has a clue instead of getting this nonsense posted to the front page of slashdot...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530943</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531337</id>
	<title>Re:Guaranteed?</title>
	<author>LWATCDR</author>
	<datestamp>1246386180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I would think something like Kermit combined with CRC checks and encryption with some scripting would do the trick..<br>Does sound like something from Tom Clancy.</p></htmltext>
<tokenext>I would think something like Kermit combined with CRC checks and encryption with some scripting would do the trick..Does sound like something from Tom Clancy .</tokentext>
<sentencetext>I would think something like Kermit combined with CRC checks and encryption with some scripting would do the trick..Does sound like something from Tom Clancy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530161</id>
	<title>UUCP</title>
	<author>Anonymous</author>
	<datestamp>1246383180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Or I guess that would be WWCP.  WWJD?</p></htmltext>
<tokenext>Or I guess that would be WWCP .
WWJD ?</tokentext>
<sentencetext>Or I guess that would be WWCP.
WWJD?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530711</id>
	<title>Re:Line endings!</title>
	<author>Anonymous</author>
	<datestamp>1246384500000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yep, I think so too!</p></htmltext>
<tokenext>Yep , I think so too !</tokentext>
<sentencetext>Yep, I think so too!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531655</id>
	<title>Transfering data on bad networks</title>
	<author>JWSmythe</author>
	<datestamp>1246387140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>
&nbsp; &nbsp; It sounds like there's a good bit of work to be done.</p><p>
&nbsp; &nbsp; The first would be to address the problems with the internal network.  There's no excuse to have problems on a LAN.  Upgrade away from hubs and consumer grade "switches".  This is an easy and affordable fix.  There are plenty of old Cisco switches available on eBay for very little money.</p><p>
&nbsp; &nbsp; I upgraded an office with 6 Cisco Catalyst 2924-M-XL-EN and 6 WS-X2924-XL-V 100baseFX fiber modules cost $300 from eBay. I used fiber to connect all the suites, which cost about $150.  $450 got rid of all their problems that the entire staff had been complaining about for years.</p><p>
&nbsp; &nbsp; I'd also recommend having a look at the radio link.  Why isn't it working properly?  Is it a line of sight problem (a tree grew in the way, maybe?), a signal or interference problem that could be resolved with a better antenna or reconfiguration?</p><p>
&nbsp; &nbsp; For a reliable protocol, you can use rsync and rsyncd.  I use this between Windows clients and Linux backup server.  rsync provides a very reliable protocol, ensuring the data was received correctly or retrying.  FTP isn't a good protocol for mission critical data.</p><p>
&nbsp; &nbsp; Myself, depending on the link, what's on each end, etc, you may consider putting a Linux machine at each site, and doing a PPP over SSH link.   It's easy, free, and very reliable.<nobr> <wbr></nobr>:)  It doesn't take reinventing the wheel, nor playing with VPN servers and clients.  rsync over this connection will work very well, and due to compression and encryption by both rsync and ssh, you'll find that it ends up being faster.  That may seem counter-intuitive, but I've found it to be true in reality.</p><p>
&nbsp; &nbsp; For a while, I was on an unreliable home connection, which apparently did a good bit of traffic shaping and some port blocking (ahh, gotta love residential providers).  I frequently saw packet loss.  Once setting up a PPP over SSH connection, I routed every machine on my home LAN through it, and all of our traffic left through one of my datacenters.  Despite adding this extra route and hops, all Internet traffic from home was faster.  Because of the magic of SSH, it actually got rid of all my packet loss.<nobr> <wbr></nobr>:)  It was still there, but SSH retried to keep the tunnel working with no losses.  Since the provider couldn't see anything that was going over the line other than encrypted data, they couldn't do any sort of traffic shaping.  I used an non-standard port number, so they couldn't even be sure of what the encrypted data was.  I had already planned on changing ports, if they should start slowing down my traffic, but they never did.  It was unidentifiable, so they left it alone.  For several things, I enjoyed 10x the normal speed, just because of the PPP over SSH tunnel.  Doing the same transfers via HTTP or FTP over the same route (but not over the SSH connection) resulted in very slow speeds.</p></htmltext>
<tokenext>    It sounds like there 's a good bit of work to be done .
    The first would be to address the problems with the internal network .
There 's no excuse to have problems on a LAN .
Upgrade away from hubs and consumer grade " switches " .
This is an easy and affordable fix .
There are plenty of old Cisco switches available on eBay for very little money .
    I upgraded an office with 6 Cisco Catalyst 2924-M-XL-EN and 6 WS-X2924-XL-V 100baseFX fiber modules cost $ 300 from eBay .
I used fiber to connect all the suites , which cost about $ 150 .
$ 450 got rid of all their problems that the entire staff had been complaining about for years .
    I 'd also recommend having a look at the radio link .
Why is n't it working properly ?
Is it a line of sight problem ( a tree grew in the way , maybe ?
) , a signal or interference problem that could be resolved with a better antenna or reconfiguration ?
    For a reliable protocol , you can use rsync and rsyncd .
I use this between Windows clients and Linux backup server .
rsync provides a very reliable protocol , ensuring the data was received correctly or retrying .
FTP is n't a good protocol for mission critical data .
    Myself , depending on the link , what 's on each end , etc , you may consider putting a Linux machine at each site , and doing a PPP over SSH link .
It 's easy , free , and very reliable .
: ) It does n't take reinventing the wheel , nor playing with VPN servers and clients .
rsync over this connection will work very well , and due to compression and encryption by both rsync and ssh , you 'll find that it ends up being faster .
That may seem counter-intuitive , but I 've found it to be true in reality .
    For a while , I was on an unreliable home connection , which apparently did a good bit of traffic shaping and some port blocking ( ahh , got ta love residential providers ) .
I frequently saw packet loss .
Once setting up a PPP over SSH connection , I routed every machine on my home LAN through it , and all of our traffic left through one of my datacenters .
Despite adding this extra route and hops , all Internet traffic from home was faster .
Because of the magic of SSH , it actually got rid of all my packet loss .
: ) It was still there , but SSH retried to keep the tunnel working with no losses .
Since the provider could n't see anything that was going over the line other than encrypted data , they could n't do any sort of traffic shaping .
I used an non-standard port number , so they could n't even be sure of what the encrypted data was .
I had already planned on changing ports , if they should start slowing down my traffic , but they never did .
It was unidentifiable , so they left it alone .
For several things , I enjoyed 10x the normal speed , just because of the PPP over SSH tunnel .
Doing the same transfers via HTTP or FTP over the same route ( but not over the SSH connection ) resulted in very slow speeds .</tokentext>
<sentencetext>
    It sounds like there's a good bit of work to be done.
    The first would be to address the problems with the internal network.
There's no excuse to have problems on a LAN.
Upgrade away from hubs and consumer grade "switches".
This is an easy and affordable fix.
There are plenty of old Cisco switches available on eBay for very little money.
    I upgraded an office with 6 Cisco Catalyst 2924-M-XL-EN and 6 WS-X2924-XL-V 100baseFX fiber modules cost $300 from eBay.
I used fiber to connect all the suites, which cost about $150.
$450 got rid of all their problems that the entire staff had been complaining about for years.
    I'd also recommend having a look at the radio link.
Why isn't it working properly?
Is it a line of sight problem (a tree grew in the way, maybe?
), a signal or interference problem that could be resolved with a better antenna or reconfiguration?
    For a reliable protocol, you can use rsync and rsyncd.
I use this between Windows clients and Linux backup server.
rsync provides a very reliable protocol, ensuring the data was received correctly or retrying.
FTP isn't a good protocol for mission critical data.
    Myself, depending on the link, what's on each end, etc, you may consider putting a Linux machine at each site, and doing a PPP over SSH link.
It's easy, free, and very reliable.
:)  It doesn't take reinventing the wheel, nor playing with VPN servers and clients.
rsync over this connection will work very well, and due to compression and encryption by both rsync and ssh, you'll find that it ends up being faster.
That may seem counter-intuitive, but I've found it to be true in reality.
    For a while, I was on an unreliable home connection, which apparently did a good bit of traffic shaping and some port blocking (ahh, gotta love residential providers).
I frequently saw packet loss.
Once setting up a PPP over SSH connection, I routed every machine on my home LAN through it, and all of our traffic left through one of my datacenters.
Despite adding this extra route and hops, all Internet traffic from home was faster.
Because of the magic of SSH, it actually got rid of all my packet loss.
:)  It was still there, but SSH retried to keep the tunnel working with no losses.
Since the provider couldn't see anything that was going over the line other than encrypted data, they couldn't do any sort of traffic shaping.
I used an non-standard port number, so they couldn't even be sure of what the encrypted data was.
I had already planned on changing ports, if they should start slowing down my traffic, but they never did.
It was unidentifiable, so they left it alone.
For several things, I enjoyed 10x the normal speed, just because of the PPP over SSH tunnel.
Doing the same transfers via HTTP or FTP over the same route (but not over the SSH connection) resulted in very slow speeds.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530965</id>
	<title>GatherBird</title>
	<author>JaneTheIgnorantSlut</author>
	<datestamp>1246385160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I telecommute and need to reliably get install images from my office down to my desktop. I have used GatherBird's Copy Large Files utility for several years, and it has worked out very well. No problems. <a href="http://www.gatherbird.com/GBMain.aspx" title="gatherbird.com" rel="nofollow">http://www.gatherbird.com/GBMain.aspx</a> [gatherbird.com]</htmltext>
<tokenext>I telecommute and need to reliably get install images from my office down to my desktop .
I have used GatherBird 's Copy Large Files utility for several years , and it has worked out very well .
No problems .
http : //www.gatherbird.com/GBMain.aspx [ gatherbird.com ]</tokentext>
<sentencetext>I telecommute and need to reliably get install images from my office down to my desktop.
I have used GatherBird's Copy Large Files utility for several years, and it has worked out very well.
No problems.
http://www.gatherbird.com/GBMain.aspx [gatherbird.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532123</id>
	<title>Re:Line endings!</title>
	<author>raddan</author>
	<datestamp>1246388760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>That is exactly the kind of answer that makes me smack my forehead.  Duh!  Good thought!</htmltext>
<tokenext>That is exactly the kind of answer that makes me smack my forehead .
Duh ! Good thought !</tokentext>
<sentencetext>That is exactly the kind of answer that makes me smack my forehead.
Duh!  Good thought!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530883</id>
	<title>straight Windows file system copy?</title>
	<author>Anonymous</author>
	<datestamp>1246384860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Seriously !!!!</p><p>That must be the most over head and unreliable method available.</p><p>Hire an IT person to setup and implement one of the following:<br>* rsync<br>* SSH (SCP/SFTP)<br>* HTTPS<br>* FTPS</p><p>And stop transferring binary files is ASCII mode !!!!</p></htmltext>
<tokenext>Seriously ! ! !
! That must be the most over head and unreliable method available.Hire an IT person to setup and implement one of the following : * rsync * SSH ( SCP/SFTP ) * HTTPS * FTPSAnd stop transferring binary files is ASCII mode ! ! !
!</tokentext>
<sentencetext>Seriously !!!
!That must be the most over head and unreliable method available.Hire an IT person to setup and implement one of the following:* rsync* SSH (SCP/SFTP)* HTTPS* FTPSAnd stop transferring binary files is ASCII mode !!!
!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533389</id>
	<title>Checksums?</title>
	<author>number11</author>
	<datestamp>1246393740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Use any common P2P file-sharing system, preferably one that doesn't require a central server.  Gnutella would work fine, I know people do this using Shareaza and Limewire, and probably any other of the clients will work.  DC would work.  I used <a href="http://sourceforge.net/projects/waste/files/" title="sourceforge.net">WASTE</a> [sourceforge.net] for a while to do this.  Probably some other P2P software would work, too.  They almost all use hash checks to ensure accurate transmission.  Set up a private file sharing network, using one folder on each end, and your files should get transferred 100\% error-free between your computers.  Should be fairly simple, just don't share C:<nobr> <wbr></nobr>:)  The only downside I can see (outside of the IT people freaking out because you've got a file-sharing program on your computer) is that they're "pull" oriented, rather than "push", so the recipient has to retrieve the files.  See also <a href="http://en.wikipedia.org/wiki/Friend-to-friend" title="wikipedia.org">Friend-to-friend</a> [wikipedia.org] and <a href="http://en.wikipedia.org/wiki/Private\_P2P" title="wikipedia.org">Private P2P</a> [wikipedia.org]</p><p>Like others have said, find out <b>why</b> your network is breaking data in transmission and fixing that would be the more direct fix, but I'm guessing OP doesn't have control over that part.</p></htmltext>
<tokenext>Use any common P2P file-sharing system , preferably one that does n't require a central server .
Gnutella would work fine , I know people do this using Shareaza and Limewire , and probably any other of the clients will work .
DC would work .
I used WASTE [ sourceforge.net ] for a while to do this .
Probably some other P2P software would work , too .
They almost all use hash checks to ensure accurate transmission .
Set up a private file sharing network , using one folder on each end , and your files should get transferred 100 \ % error-free between your computers .
Should be fairly simple , just do n't share C : : ) The only downside I can see ( outside of the IT people freaking out because you 've got a file-sharing program on your computer ) is that they 're " pull " oriented , rather than " push " , so the recipient has to retrieve the files .
See also Friend-to-friend [ wikipedia.org ] and Private P2P [ wikipedia.org ] Like others have said , find out why your network is breaking data in transmission and fixing that would be the more direct fix , but I 'm guessing OP does n't have control over that part .</tokentext>
<sentencetext>Use any common P2P file-sharing system, preferably one that doesn't require a central server.
Gnutella would work fine, I know people do this using Shareaza and Limewire, and probably any other of the clients will work.
DC would work.
I used WASTE [sourceforge.net] for a while to do this.
Probably some other P2P software would work, too.
They almost all use hash checks to ensure accurate transmission.
Set up a private file sharing network, using one folder on each end, and your files should get transferred 100\% error-free between your computers.
Should be fairly simple, just don't share C: :)  The only downside I can see (outside of the IT people freaking out because you've got a file-sharing program on your computer) is that they're "pull" oriented, rather than "push", so the recipient has to retrieve the files.
See also Friend-to-friend [wikipedia.org] and Private P2P [wikipedia.org]Like others have said, find out why your network is breaking data in transmission and fixing that would be the more direct fix, but I'm guessing OP doesn't have control over that part.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530145</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532669</id>
	<title>Robocopy</title>
	<author>flyingfsck</author>
	<datestamp>1246390620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Robocopy is commonly used for this problem.

Otherwise Cygwin and rsync.</htmltext>
<tokenext>Robocopy is commonly used for this problem .
Otherwise Cygwin and rsync .</tokentext>
<sentencetext>Robocopy is commonly used for this problem.
Otherwise Cygwin and rsync.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530999</id>
	<title>Use openvpn..</title>
	<author>miknix</author>
	<datestamp>1246385220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Establish a openvpn tunnel over UDP. All network traffic tunneled through it, will be encrypted and with integrity ensured. If your wireless network link is too unstable, you will have plenty of dis/re-connections of openvpn but communications going through the tunnel will be intact.</p><p>For example, one day I connected home over openvpn and used nfs to transfer a couple of big files over a slow wireless link. After some time going on, I closed my laptop and put it into suspend and moved into another place and connected to another wireless link. After resuming the laptop, openvpn re-established the connection to home and nfs continued to copy the file.</p></htmltext>
<tokenext>Establish a openvpn tunnel over UDP .
All network traffic tunneled through it , will be encrypted and with integrity ensured .
If your wireless network link is too unstable , you will have plenty of dis/re-connections of openvpn but communications going through the tunnel will be intact.For example , one day I connected home over openvpn and used nfs to transfer a couple of big files over a slow wireless link .
After some time going on , I closed my laptop and put it into suspend and moved into another place and connected to another wireless link .
After resuming the laptop , openvpn re-established the connection to home and nfs continued to copy the file .</tokentext>
<sentencetext>Establish a openvpn tunnel over UDP.
All network traffic tunneled through it, will be encrypted and with integrity ensured.
If your wireless network link is too unstable, you will have plenty of dis/re-connections of openvpn but communications going through the tunnel will be intact.For example, one day I connected home over openvpn and used nfs to transfer a couple of big files over a slow wireless link.
After some time going on, I closed my laptop and put it into suspend and moved into another place and connected to another wireless link.
After resuming the laptop, openvpn re-established the connection to home and nfs continued to copy the file.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536267</id>
	<title>Re:You're kidding, aren't you??</title>
	<author>Anonymous</author>
	<datestamp>1246364160000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>Hmmm....  Here's a thought?  What if the "Mission" is something related to a some sort of military activity and the data that is "Critical" is held in a location with spotty connectivity and severely constrained bandwidth (say a beach position with a little satellite dish).  I am sure your hand washing memo will be very well received by all those folks who are put in harms way because of your willingness to make it someone else's problem.</p><p>You simply cannot assume away the problem or try and fit the problem to meet your expectations.  Microsoft and IBM have made a reputation on trying this approach, but reality has this nasty habit of ultimately dictating the terms of the problem in spite of whatever massive resources are expended to the contrary.</p><p>Technical work arounds are the nature of the beast in the "real world".  Perhaps a dose of exposure there will give you a little more empathy and perspective from which to approach these types of issues in the future.</p><p>I don't feel like registering at the moment, so I guess I will go with Anonymous Coward for now... (Tom for short)<nobr> <wbr></nobr>:')</p></htmltext>
<tokenext>Hmmm.... Here 's a thought ?
What if the " Mission " is something related to a some sort of military activity and the data that is " Critical " is held in a location with spotty connectivity and severely constrained bandwidth ( say a beach position with a little satellite dish ) .
I am sure your hand washing memo will be very well received by all those folks who are put in harms way because of your willingness to make it someone else 's problem.You simply can not assume away the problem or try and fit the problem to meet your expectations .
Microsoft and IBM have made a reputation on trying this approach , but reality has this nasty habit of ultimately dictating the terms of the problem in spite of whatever massive resources are expended to the contrary.Technical work arounds are the nature of the beast in the " real world " .
Perhaps a dose of exposure there will give you a little more empathy and perspective from which to approach these types of issues in the future.I do n't feel like registering at the moment , so I guess I will go with Anonymous Coward for now... ( Tom for short ) : ' )</tokentext>
<sentencetext>Hmmm....  Here's a thought?
What if the "Mission" is something related to a some sort of military activity and the data that is "Critical" is held in a location with spotty connectivity and severely constrained bandwidth (say a beach position with a little satellite dish).
I am sure your hand washing memo will be very well received by all those folks who are put in harms way because of your willingness to make it someone else's problem.You simply cannot assume away the problem or try and fit the problem to meet your expectations.
Microsoft and IBM have made a reputation on trying this approach, but reality has this nasty habit of ultimately dictating the terms of the problem in spite of whatever massive resources are expended to the contrary.Technical work arounds are the nature of the beast in the "real world".
Perhaps a dose of exposure there will give you a little more empathy and perspective from which to approach these types of issues in the future.I don't feel like registering at the moment, so I guess I will go with Anonymous Coward for now... (Tom for short) :')</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531411</id>
	<title>Files smaller from FTP?</title>
	<author>Anonymous</author>
	<datestamp>1246386420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Ummm... try using the "BINARY" command in the FTP client first?</p></htmltext>
<tokenext>Ummm... try using the " BINARY " command in the FTP client first ?</tokentext>
<sentencetext>Ummm... try using the "BINARY" command in the FTP client first?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533639</id>
	<title>Guaranteed transmission in downloads</title>
	<author>ant\_tmwx</author>
	<datestamp>1246394880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You can use <a href="http://www.metalinker.org/" title="metalinker.org" rel="nofollow">Metalinks</a> [metalinker.org] for downloads without errors. It can use whole file checksums, or partial file checksums to repair errors.</p></htmltext>
<tokenext>You can use Metalinks [ metalinker.org ] for downloads without errors .
It can use whole file checksums , or partial file checksums to repair errors .</tokentext>
<sentencetext>You can use Metalinks [metalinker.org] for downloads without errors.
It can use whole file checksums, or partial file checksums to repair errors.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531707</id>
	<title>It warms my heart to see noob mistakes</title>
	<author>Anonymous</author>
	<datestamp>1246387320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Economy, eschmonomy.</p><p>Seeing this problem and some of the hilariously incorrect answers ensure that regardless of this downturn, I'd have job prospects if I was out of work.</p><p>Thanks ignorance!</p></htmltext>
<tokenext>Economy , eschmonomy.Seeing this problem and some of the hilariously incorrect answers ensure that regardless of this downturn , I 'd have job prospects if I was out of work.Thanks ignorance !</tokentext>
<sentencetext>Economy, eschmonomy.Seeing this problem and some of the hilariously incorrect answers ensure that regardless of this downturn, I'd have job prospects if I was out of work.Thanks ignorance!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530927</id>
	<title>mod k0p</title>
	<author>Anonymous</author>
	<datestamp>1246384980000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext><A HREF="http://goat.cx/" title="goat.cx" rel="nofollow">they wa8t you to</a> [goat.cx]</htmltext>
<tokenext>they wa8t you to [ goat.cx ]</tokentext>
<sentencetext>they wa8t you to [goat.cx]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542189</id>
	<title>Good windows transfer program</title>
	<author>Malenx</author>
	<datestamp>1246462500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Terracopy is a great program for copying files inside windows.  It does error checking and supports resume if your connection drops.</p><p>You can download the home edition at <a href="http://www.terracopy.com/" title="terracopy.com" rel="nofollow">http://www.terracopy.com/</a> [terracopy.com] to give it a try.</p><p>I had issues with copying about 300gb of backups around different servers until I installed that, works great.</p></htmltext>
<tokenext>Terracopy is a great program for copying files inside windows .
It does error checking and supports resume if your connection drops.You can download the home edition at http : //www.terracopy.com/ [ terracopy.com ] to give it a try.I had issues with copying about 300gb of backups around different servers until I installed that , works great .</tokentext>
<sentencetext>Terracopy is a great program for copying files inside windows.
It does error checking and supports resume if your connection drops.You can download the home edition at http://www.terracopy.com/ [terracopy.com] to give it a try.I had issues with copying about 300gb of backups around different servers until I installed that, works great.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533303</id>
	<title>Use WiNRAR</title>
	<author>Anonymous</author>
	<datestamp>1246393380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Use Winrar to compress and archive a group of files into one files - plus turn on recovery record so if during transmission of your files - if a corruption occurs the recovery record can figure it out.</p><p>Then use ftp/etc to transmit your file across</p></htmltext>
<tokenext>Use Winrar to compress and archive a group of files into one files - plus turn on recovery record so if during transmission of your files - if a corruption occurs the recovery record can figure it out.Then use ftp/etc to transmit your file across</tokentext>
<sentencetext>Use Winrar to compress and archive a group of files into one files - plus turn on recovery record so if during transmission of your files - if a corruption occurs the recovery record can figure it out.Then use ftp/etc to transmit your file across</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530305</id>
	<title>First Off</title>
	<author>DaMattster</author>
	<datestamp>1246383540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>There are no guarantees when it comes to the protocols and the internet<nobr> <wbr></nobr>.... it is always a "best effort" system.  Many forget that it is always a best effort system because the internet has come to the point where for all intents and purposes, there are virtually no failures.  I would probably use a tried and true protocol like FTP or maybe even SCP.  Both work very well.  I would think your best bet is to try to work with the government to improve their "dodgy" internal network.  SCP has the advantage of securing the transmission as well as excellent error correction and recovery.</htmltext>
<tokenext>There are no guarantees when it comes to the protocols and the internet .... it is always a " best effort " system .
Many forget that it is always a best effort system because the internet has come to the point where for all intents and purposes , there are virtually no failures .
I would probably use a tried and true protocol like FTP or maybe even SCP .
Both work very well .
I would think your best bet is to try to work with the government to improve their " dodgy " internal network .
SCP has the advantage of securing the transmission as well as excellent error correction and recovery .</tokentext>
<sentencetext>There are no guarantees when it comes to the protocols and the internet .... it is always a "best effort" system.
Many forget that it is always a best effort system because the internet has come to the point where for all intents and purposes, there are virtually no failures.
I would probably use a tried and true protocol like FTP or maybe even SCP.
Both work very well.
I would think your best bet is to try to work with the government to improve their "dodgy" internal network.
SCP has the advantage of securing the transmission as well as excellent error correction and recovery.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532821</id>
	<title>Re:Guaranteed?</title>
	<author>KraftDinner</author>
	<datestamp>1246391220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Hahahaha, it's funny because he got 150 years.</htmltext>
<tokenext>Hahahaha , it 's funny because he got 150 years .</tokentext>
<sentencetext>Hahahaha, it's funny because he got 150 years.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530943</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534005</id>
	<title>Windows-Windows copy?  I have the answer.</title>
	<author>AppleTwoGuru</author>
	<datestamp>1246353180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What you will want to do if you have a Windows machine on each end, is to secure each machine first. That would mean, over-writing the Windows operating system with a Unix/Unix-like system (Linux, BSD, Solaris, Hack-Mac). Then you have (most likely) built-in SFTP servers and clients. That is what I would do. Someone would eventually hack into your Windows system. That is the way Windows is, so that MS or an MS-partner can sell you the antidote to your virus woes (even after your cure your woes, they will come up with something another virus so as to sell you another cure to get your money.) Get security right from the start instead of an add-on. Go with Unix or a Unix clone.</htmltext>
<tokenext>What you will want to do if you have a Windows machine on each end , is to secure each machine first .
That would mean , over-writing the Windows operating system with a Unix/Unix-like system ( Linux , BSD , Solaris , Hack-Mac ) .
Then you have ( most likely ) built-in SFTP servers and clients .
That is what I would do .
Someone would eventually hack into your Windows system .
That is the way Windows is , so that MS or an MS-partner can sell you the antidote to your virus woes ( even after your cure your woes , they will come up with something another virus so as to sell you another cure to get your money .
) Get security right from the start instead of an add-on .
Go with Unix or a Unix clone .</tokentext>
<sentencetext>What you will want to do if you have a Windows machine on each end, is to secure each machine first.
That would mean, over-writing the Windows operating system with a Unix/Unix-like system (Linux, BSD, Solaris, Hack-Mac).
Then you have (most likely) built-in SFTP servers and clients.
That is what I would do.
Someone would eventually hack into your Windows system.
That is the way Windows is, so that MS or an MS-partner can sell you the antidote to your virus woes (even after your cure your woes, they will come up with something another virus so as to sell you another cure to get your money.
) Get security right from the start instead of an add-on.
Go with Unix or a Unix clone.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531021</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246385280000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Size differences could just be due to different block sizes on the disk, depending on how windows reports things. Do an md5sum or equivalent to verify file contents.</p></htmltext>
<tokenext>Size differences could just be due to different block sizes on the disk , depending on how windows reports things .
Do an md5sum or equivalent to verify file contents .</tokentext>
<sentencetext>Size differences could just be due to different block sizes on the disk, depending on how windows reports things.
Do an md5sum or equivalent to verify file contents.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532913</id>
	<title>Differences in storage sizes / AFT</title>
	<author>charnov</author>
	<datestamp>1246391640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Have you checked that the differences in files sizes aren't due to the differences in cluster size?</p><p>You can verify content by simply comparing hash values. If you need more assurance, then Sterling Managed File Transfer, or SFTP.</p><p>If you are talking DoD, DoE, or anything above a confidential level... for the love of God, call the NSA and request to use Assured File Transfer (AFT) or some other managed system. They should help you with this.</p></htmltext>
<tokenext>Have you checked that the differences in files sizes are n't due to the differences in cluster size ? You can verify content by simply comparing hash values .
If you need more assurance , then Sterling Managed File Transfer , or SFTP.If you are talking DoD , DoE , or anything above a confidential level... for the love of God , call the NSA and request to use Assured File Transfer ( AFT ) or some other managed system .
They should help you with this .</tokentext>
<sentencetext>Have you checked that the differences in files sizes aren't due to the differences in cluster size?You can verify content by simply comparing hash values.
If you need more assurance, then Sterling Managed File Transfer, or SFTP.If you are talking DoD, DoE, or anything above a confidential level... for the love of God, call the NSA and request to use Assured File Transfer (AFT) or some other managed system.
They should help you with this.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538205</id>
	<title>Re:UDP.</title>
	<author>GMC-jimmy</author>
	<datestamp>1246378860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think the original poster intended to ask about a client application protocol. Like their reference to FTP. If my assumption is correct, then the poster from the article might be interested in something like <a href="http://www.samba.org/rsync/features.html" title="samba.org">rsync</a> [samba.org], only for Windows instead of Unix. In which that case would be <a href="http://www.itefix.no/i2/node/10650" title="itefix.no">cwrsync - Rsync for Windows</a> [itefix.no].</p><p>I invested more time in making this post than researching file transfer solutions for this article. More research by the interested party would be wise.</p></htmltext>
<tokenext>I think the original poster intended to ask about a client application protocol .
Like their reference to FTP .
If my assumption is correct , then the poster from the article might be interested in something like rsync [ samba.org ] , only for Windows instead of Unix .
In which that case would be cwrsync - Rsync for Windows [ itefix.no ] .I invested more time in making this post than researching file transfer solutions for this article .
More research by the interested party would be wise .</tokentext>
<sentencetext>I think the original poster intended to ask about a client application protocol.
Like their reference to FTP.
If my assumption is correct, then the poster from the article might be interested in something like rsync [samba.org], only for Windows instead of Unix.
In which that case would be cwrsync - Rsync for Windows [itefix.no].I invested more time in making this post than researching file transfer solutions for this article.
More research by the interested party would be wise.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530937</id>
	<title>Most Guaranteed To Work:</title>
	<author>Anonymous</author>
	<datestamp>1246385040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>is Snail Mail.</p><p>Yours In Capitalism,<br>Kilgore Trout</p></htmltext>
<tokenext>is Snail Mail.Yours In Capitalism,Kilgore Trout</tokentext>
<sentencetext>is Snail Mail.Yours In Capitalism,Kilgore Trout</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533477</id>
	<title>And you're trolling</title>
	<author>Anonymous</author>
	<datestamp>1246394160000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"mission critical" can mean different levels of paranoia depending on the mission.</p><p>Perhaps this guy's mission is backing up his pr0n - and his current backup approach is almost good enough for that mission, though it's a bit frustrating.</p><p>Other missions might demand digging a concrete trench and laying your own fiber between the computers he's trying to back up (say, if your mission is so important it has to survive the collapse of the major phone companies).</p><p>In most real businesses, though, a failed copy of mission critical data often results in a dissatisfied customer and the resulting customer service damage control -- for which most of the advice on this slashdot thread (rsync, etc) seem appropriate levels of protection.</p></htmltext>
<tokenext>" mission critical " can mean different levels of paranoia depending on the mission.Perhaps this guy 's mission is backing up his pr0n - and his current backup approach is almost good enough for that mission , though it 's a bit frustrating.Other missions might demand digging a concrete trench and laying your own fiber between the computers he 's trying to back up ( say , if your mission is so important it has to survive the collapse of the major phone companies ) .In most real businesses , though , a failed copy of mission critical data often results in a dissatisfied customer and the resulting customer service damage control -- for which most of the advice on this slashdot thread ( rsync , etc ) seem appropriate levels of protection .</tokentext>
<sentencetext>"mission critical" can mean different levels of paranoia depending on the mission.Perhaps this guy's mission is backing up his pr0n - and his current backup approach is almost good enough for that mission, though it's a bit frustrating.Other missions might demand digging a concrete trench and laying your own fiber between the computers he's trying to back up (say, if your mission is so important it has to survive the collapse of the major phone companies).In most real businesses, though, a failed copy of mission critical data often results in a dissatisfied customer and the resulting customer service damage control -- for which most of the advice on this slashdot thread (rsync, etc) seem appropriate levels of protection.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532581</id>
	<title>Re:TCP?</title>
	<author>sexconker</author>
	<datestamp>1246390320000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>Windows reports file sizes exactly, to the byte.</p><p>It reports both the true file size and the file size on the disk, which is based on the block size and the number of blocks required to store the file.</p></htmltext>
<tokenext>Windows reports file sizes exactly , to the byte.It reports both the true file size and the file size on the disk , which is based on the block size and the number of blocks required to store the file .</tokentext>
<sentencetext>Windows reports file sizes exactly, to the byte.It reports both the true file size and the file size on the disk, which is based on the block size and the number of blocks required to store the file.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538229</id>
	<title>Connect:Direct by Sterling Software</title>
	<author>Anonymous</author>
	<datestamp>1246379100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I work at a company with thousands of servers - Solaris, Windows, mainframe, even VMS.  Connect:Direct runs on all of them.  It costs, and it's not the easiest to script, but when you want the file to get there, and want to know exactly when it got there, it's the way to go.</p><p>(I have no financial interest or connection to Sterling Software.)</p></htmltext>
<tokenext>I work at a company with thousands of servers - Solaris , Windows , mainframe , even VMS .
Connect : Direct runs on all of them .
It costs , and it 's not the easiest to script , but when you want the file to get there , and want to know exactly when it got there , it 's the way to go .
( I have no financial interest or connection to Sterling Software .
)</tokentext>
<sentencetext>I work at a company with thousands of servers - Solaris, Windows, mainframe, even VMS.
Connect:Direct runs on all of them.
It costs, and it's not the easiest to script, but when you want the file to get there, and want to know exactly when it got there, it's the way to go.
(I have no financial interest or connection to Sterling Software.
)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531997</id>
	<title>Re:UDP.</title>
	<author>Anonymous</author>
	<datestamp>1246388340000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Only slashdot can tag this response as a 5 Funny!<nobr> <wbr></nobr>;)</p><p>p.s. Make sure to disable UDP checksums.</p></htmltext>
<tokenext>Only slashdot can tag this response as a 5 Funny !
; ) p.s. Make sure to disable UDP checksums .</tokentext>
<sentencetext>Only slashdot can tag this response as a 5 Funny!
;)p.s. Make sure to disable UDP checksums.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533153</id>
	<title>Tune your TCP and FTP</title>
	<author>kbielefe</author>
	<datestamp>1246392660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Most modern networks expect a highly reliable data link with congestion as the primary concern, and are tuned accordingly.  You have a highly unreliable data link with little concern about congestion (assuming the microwave link rarely if ever has more than one simultaneous user).  The problem is that when a packet is corrupted or lost, the transmitter assumes a crowded pipe and starts slowing down, when you really want it to retransmit as soon as possible.  Since it's doing the exact opposite of what's needed to fix the problem, it can compound on itself out of control, eventually causing it to just give up the file transfer altogether.  Therefore, you want a short retransmission timeout for TCP, a longer timeout for FTP (or whatever better application layer many people have recommended you try), and a smaller MTU so there is a lower probability of any one given packet getting corrupted or lost.</p><p>Of course, you can go too far the other way too, and the ideal settings are going to be highly dependent on your individual network.</p></htmltext>
<tokenext>Most modern networks expect a highly reliable data link with congestion as the primary concern , and are tuned accordingly .
You have a highly unreliable data link with little concern about congestion ( assuming the microwave link rarely if ever has more than one simultaneous user ) .
The problem is that when a packet is corrupted or lost , the transmitter assumes a crowded pipe and starts slowing down , when you really want it to retransmit as soon as possible .
Since it 's doing the exact opposite of what 's needed to fix the problem , it can compound on itself out of control , eventually causing it to just give up the file transfer altogether .
Therefore , you want a short retransmission timeout for TCP , a longer timeout for FTP ( or whatever better application layer many people have recommended you try ) , and a smaller MTU so there is a lower probability of any one given packet getting corrupted or lost.Of course , you can go too far the other way too , and the ideal settings are going to be highly dependent on your individual network .</tokentext>
<sentencetext>Most modern networks expect a highly reliable data link with congestion as the primary concern, and are tuned accordingly.
You have a highly unreliable data link with little concern about congestion (assuming the microwave link rarely if ever has more than one simultaneous user).
The problem is that when a packet is corrupted or lost, the transmitter assumes a crowded pipe and starts slowing down, when you really want it to retransmit as soon as possible.
Since it's doing the exact opposite of what's needed to fix the problem, it can compound on itself out of control, eventually causing it to just give up the file transfer altogether.
Therefore, you want a short retransmission timeout for TCP, a longer timeout for FTP (or whatever better application layer many people have recommended you try), and a smaller MTU so there is a lower probability of any one given packet getting corrupted or lost.Of course, you can go too far the other way too, and the ideal settings are going to be highly dependent on your individual network.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532591</id>
	<title>TeraCopy</title>
	<author>Anonymous</author>
	<datestamp>1246390320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Uhh... Easy....   Teracopy</p><p><a href="http://www.codesector.com/teracopy.php" title="codesector.com" rel="nofollow">http://www.codesector.com/teracopy.php</a> [codesector.com]</p><p>-Josh</p></htmltext>
<tokenext>Uhh... Easy.... Teracopyhttp : //www.codesector.com/teracopy.php [ codesector.com ] -Josh</tokentext>
<sentencetext>Uhh... Easy....   Teracopyhttp://www.codesector.com/teracopy.php [codesector.com]-Josh</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</id>
	<title>TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246383180000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>The summary states that with FTP, the downloaded files were of the wrong size.  Can anyone explain why TCP's efforts to to deal with unreliable networks, such as the retransmission of unacknowledged packets and their reassembly in proper order, would not already deal with this?  I am familiar with the concepts involved but I think I lack the low-level understanding of how you would get the kind of results the story is reporting.</htmltext>
<tokenext>The summary states that with FTP , the downloaded files were of the wrong size .
Can anyone explain why TCP 's efforts to to deal with unreliable networks , such as the retransmission of unacknowledged packets and their reassembly in proper order , would not already deal with this ?
I am familiar with the concepts involved but I think I lack the low-level understanding of how you would get the kind of results the story is reporting .</tokentext>
<sentencetext>The summary states that with FTP, the downloaded files were of the wrong size.
Can anyone explain why TCP's efforts to to deal with unreliable networks, such as the retransmission of unacknowledged packets and their reassembly in proper order, would not already deal with this?
I am familiar with the concepts involved but I think I lack the low-level understanding of how you would get the kind of results the story is reporting.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539757</id>
	<title>Waste</title>
	<author>Anonymous</author>
	<datestamp>1246441080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>How about a version of waste like http://waste.sourceforge.net/ or http://wasteagain.sourceforge.net/ ? It's encrypted and if the network connection drops, the transfer just restarts when the connection comes up again.</p></htmltext>
<tokenext>How about a version of waste like http : //waste.sourceforge.net/ or http : //wasteagain.sourceforge.net/ ?
It 's encrypted and if the network connection drops , the transfer just restarts when the connection comes up again .</tokentext>
<sentencetext>How about a version of waste like http://waste.sourceforge.net/ or http://wasteagain.sourceforge.net/ ?
It's encrypted and if the network connection drops, the transfer just restarts when the connection comes up again.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531131</id>
	<title>Re:Line endings!</title>
	<author>wick3t</author>
	<datestamp>1246385580000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>
Twenty bucks says you're converting from DOS line endings (\r\n) to Unix line endings (\n).
</p></div><p>There, fixed that for you.</p></div>
	</htmltext>
<tokenext>Twenty bucks says you 're converting from DOS line endings ( \ r \ n ) to Unix line endings ( \ n ) .
There , fixed that for you .</tokentext>
<sentencetext>
Twenty bucks says you're converting from DOS line endings (\r\n) to Unix line endings (\n).
There, fixed that for you.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530221</id>
	<title>WebDAV better than FTP</title>
	<author>Anonymous</author>
	<datestamp>1246383300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You can run over an SSL link. Plain-old FTP would be the worst choice as anyone could sniff your traffic.</p></htmltext>
<tokenext>You can run over an SSL link .
Plain-old FTP would be the worst choice as anyone could sniff your traffic .</tokentext>
<sentencetext>You can run over an SSL link.
Plain-old FTP would be the worst choice as anyone could sniff your traffic.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530865</id>
	<title>AS2 FTW</title>
	<author>Anonymous</author>
	<datestamp>1246384860000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>You should look at the <a href="http://en.wikipedia.org/wiki/AS2#AS2\_Technical\_Overview" title="wikipedia.org">EDIINT AS2 protocol</a> [wikipedia.org], AKA <a href="http://www.ietf.org/rfc/rfc4130.txt" title="ietf.org">RFC 4130</a> [ietf.org].  This is a widely-used e-commerce protocol built over HTTP/S.</p><p>AS2 provides cryptographic signatures for authentification of the file at reception, non-repudiation and message delivery confirmation (if no confirmation is returned, the transfer is considered a failure), and is geared towards files.   There is even an open-source implementation avaliable.</p><p>More complex than FTP/SFTP but entirely worth it if your data is mission-critical and/or confidential.  Plus, passes through most networks because it is based on HTTP.</p></htmltext>
<tokenext>You should look at the EDIINT AS2 protocol [ wikipedia.org ] , AKA RFC 4130 [ ietf.org ] .
This is a widely-used e-commerce protocol built over HTTP/S.AS2 provides cryptographic signatures for authentification of the file at reception , non-repudiation and message delivery confirmation ( if no confirmation is returned , the transfer is considered a failure ) , and is geared towards files .
There is even an open-source implementation avaliable.More complex than FTP/SFTP but entirely worth it if your data is mission-critical and/or confidential .
Plus , passes through most networks because it is based on HTTP .</tokentext>
<sentencetext>You should look at the EDIINT AS2 protocol [wikipedia.org], AKA RFC 4130 [ietf.org].
This is a widely-used e-commerce protocol built over HTTP/S.AS2 provides cryptographic signatures for authentification of the file at reception, non-repudiation and message delivery confirmation (if no confirmation is returned, the transfer is considered a failure), and is geared towards files.
There is even an open-source implementation avaliable.More complex than FTP/SFTP but entirely worth it if your data is mission-critical and/or confidential.
Plus, passes through most networks because it is based on HTTP.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534641</id>
	<title>MQ-Series, period.</title>
	<author>Anonymous</author>
	<datestamp>1246355640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>MQ-Series for guaranteed transactions.<br>CONNECT:Direct for guaranteed file transfers.</p><p>These are what telecoms, insurance companies and banks use.</p><p>You can play around with other solutions and validation/retry scripts if you like.  At home, I do this.  At work, I use things that work, every time and recover from failures.</p></htmltext>
<tokenext>MQ-Series for guaranteed transactions.CONNECT : Direct for guaranteed file transfers.These are what telecoms , insurance companies and banks use.You can play around with other solutions and validation/retry scripts if you like .
At home , I do this .
At work , I use things that work , every time and recover from failures .</tokentext>
<sentencetext>MQ-Series for guaranteed transactions.CONNECT:Direct for guaranteed file transfers.These are what telecoms, insurance companies and banks use.You can play around with other solutions and validation/retry scripts if you like.
At home, I do this.
At work, I use things that work, every time and recover from failures.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542813</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246465200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"and anything that can be automated should be."</p><p>Except train control on Washington's Metro subway.</p></htmltext>
<tokenext>" and anything that can be automated should be .
" Except train control on Washington 's Metro subway .</tokentext>
<sentencetext>"and anything that can be automated should be.
"Except train control on Washington's Metro subway.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531923</id>
	<title>Re:UDP.</title>
	<author>Anonymous</author>
	<datestamp>1246388100000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>TCP is so horrible. I wish HTTP used UDP by default so I wouldn't have the pro</p></htmltext>
<tokenext>TCP is so horrible .
I wish HTTP used UDP by default so I would n't have the pro</tokentext>
<sentencetext>TCP is so horrible.
I wish HTTP used UDP by default so I wouldn't have the pro</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532353</id>
	<title>Kermit</title>
	<author>madfilipino</author>
	<datestamp>1246389600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It's old but highly reliable and can be secured.</htmltext>
<tokenext>It 's old but highly reliable and can be secured .</tokentext>
<sentencetext>It's old but highly reliable and can be secured.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532081</id>
	<title>Re:Line endings!</title>
	<author>greed</author>
	<datestamp>1246388640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Text mode on Windows is worse than that.</p><p>CTRL-Z (032, 26, 0x1a, ASCII SUB) terminates a text stream.</p><p>Plus, others have said round-trip should be OK.  But you're not:</p><p>CR-LF -&gt; LF -&gt; CR-LF<br>LF -&gt; LF -&gt; CR-LF</p><p>Windows text mode should have been left in the early 80s where it belonged.  Everyone else went to out-of-band EOF and single-character EOL marks.  (Not necessarily the same EOL marks; I've seen CR, LF, and RS over the years.)</p><p>(Even Windows really uses out-of-band EOF, the CTRL-Z thing is Legacy.  But it still affects text streams.  Usually.)</p></htmltext>
<tokenext>Text mode on Windows is worse than that.CTRL-Z ( 032 , 26 , 0x1a , ASCII SUB ) terminates a text stream.Plus , others have said round-trip should be OK. But you 're not : CR-LF - &gt; LF - &gt; CR-LFLF - &gt; LF - &gt; CR-LFWindows text mode should have been left in the early 80s where it belonged .
Everyone else went to out-of-band EOF and single-character EOL marks .
( Not necessarily the same EOL marks ; I 've seen CR , LF , and RS over the years .
) ( Even Windows really uses out-of-band EOF , the CTRL-Z thing is Legacy .
But it still affects text streams .
Usually. )</tokentext>
<sentencetext>Text mode on Windows is worse than that.CTRL-Z (032, 26, 0x1a, ASCII SUB) terminates a text stream.Plus, others have said round-trip should be OK.  But you're not:CR-LF -&gt; LF -&gt; CR-LFLF -&gt; LF -&gt; CR-LFWindows text mode should have been left in the early 80s where it belonged.
Everyone else went to out-of-band EOF and single-character EOL marks.
(Not necessarily the same EOL marks; I've seen CR, LF, and RS over the years.
)(Even Windows really uses out-of-band EOF, the CTRL-Z thing is Legacy.
But it still affects text streams.
Usually.)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532263</id>
	<title>Bittorrent</title>
	<author>sexconker</author>
	<datestamp>1246389300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Bittorrent?<br>Also, 2 mbit microwave wtf.<br>Run a cable for shit's sake.</p></htmltext>
<tokenext>Bittorrent ? Also , 2 mbit microwave wtf.Run a cable for shit 's sake .</tokentext>
<sentencetext>Bittorrent?Also, 2 mbit microwave wtf.Run a cable for shit's sake.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531487</id>
	<title>Re:TCP?</title>
	<author>Ant P.</author>
	<datestamp>1246386540000</datestamp>
	<modclass>Troll</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>Nothing wrong with the protocol</p></div><p>Sorry, but any protocol that <em>corrupts data</em> because a notepad.exe compatibility switch was set the wrong way is just completely fucked up.</p></div>
	</htmltext>
<tokenext>Nothing wrong with the protocolSorry , but any protocol that corrupts data because a notepad.exe compatibility switch was set the wrong way is just completely fucked up .</tokentext>
<sentencetext>Nothing wrong with the protocolSorry, but any protocol that corrupts data because a notepad.exe compatibility switch was set the wrong way is just completely fucked up.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531257</id>
	<title>FTP is fairly reliable...</title>
	<author>laird</author>
	<datestamp>1246385940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If the files are often the wrong size, it's probably something like CR/LF translation, or shifting reported file size due to filesystem block size. What do you see if you compare the files? Do they have the same checksum on both systems? My guess is that you don't have a tools problem (FTP, lame as it is, is probably not having as many transmission errors as you describe).</p><p>In terms of file copying tools, the options that come to mind are:</p><p>FTP doesn't check data integrity, but it's fairly reliable nonetheless, due to the TCP layer, which does retransmission, etc. But if there are transmission errors you may not be notified (i.e. you won't know if there's corruption, but you will be told if the connection dropped. So don't use it.</p><p>SCP does check data integrity, so if there's a problem in transmission it'll detect it and tell you, but it won't correct the error - you'll have to script re-sending if there's an error.</p><p>rsync checks the integrity of each delivered file, which is great. That being said, rsync is really designed to duplicate a directory tree from one machine to another, not copy individual files, so you may need to play with it a bit to do what you want.</p><p>Pando (http://www.pando.com) gives you the above plus data validation and retransmission, which might help in your situation. I've used it when sending very large files over unreliable connections (e.g. dial, weak wireless) and it'll keep hammering away until the data gets through. It's primarily a GUI app (Windows, Mac, Linux) so it's more of a consumer tool, but it can be scripted, etc., so depending on your application it might be what you want.</p></htmltext>
<tokenext>If the files are often the wrong size , it 's probably something like CR/LF translation , or shifting reported file size due to filesystem block size .
What do you see if you compare the files ?
Do they have the same checksum on both systems ?
My guess is that you do n't have a tools problem ( FTP , lame as it is , is probably not having as many transmission errors as you describe ) .In terms of file copying tools , the options that come to mind are : FTP does n't check data integrity , but it 's fairly reliable nonetheless , due to the TCP layer , which does retransmission , etc .
But if there are transmission errors you may not be notified ( i.e .
you wo n't know if there 's corruption , but you will be told if the connection dropped .
So do n't use it.SCP does check data integrity , so if there 's a problem in transmission it 'll detect it and tell you , but it wo n't correct the error - you 'll have to script re-sending if there 's an error.rsync checks the integrity of each delivered file , which is great .
That being said , rsync is really designed to duplicate a directory tree from one machine to another , not copy individual files , so you may need to play with it a bit to do what you want.Pando ( http : //www.pando.com ) gives you the above plus data validation and retransmission , which might help in your situation .
I 've used it when sending very large files over unreliable connections ( e.g .
dial , weak wireless ) and it 'll keep hammering away until the data gets through .
It 's primarily a GUI app ( Windows , Mac , Linux ) so it 's more of a consumer tool , but it can be scripted , etc. , so depending on your application it might be what you want .</tokentext>
<sentencetext>If the files are often the wrong size, it's probably something like CR/LF translation, or shifting reported file size due to filesystem block size.
What do you see if you compare the files?
Do they have the same checksum on both systems?
My guess is that you don't have a tools problem (FTP, lame as it is, is probably not having as many transmission errors as you describe).In terms of file copying tools, the options that come to mind are:FTP doesn't check data integrity, but it's fairly reliable nonetheless, due to the TCP layer, which does retransmission, etc.
But if there are transmission errors you may not be notified (i.e.
you won't know if there's corruption, but you will be told if the connection dropped.
So don't use it.SCP does check data integrity, so if there's a problem in transmission it'll detect it and tell you, but it won't correct the error - you'll have to script re-sending if there's an error.rsync checks the integrity of each delivered file, which is great.
That being said, rsync is really designed to duplicate a directory tree from one machine to another, not copy individual files, so you may need to play with it a bit to do what you want.Pando (http://www.pando.com) gives you the above plus data validation and retransmission, which might help in your situation.
I've used it when sending very large files over unreliable connections (e.g.
dial, weak wireless) and it'll keep hammering away until the data gets through.
It's primarily a GUI app (Windows, Mac, Linux) so it's more of a consumer tool, but it can be scripted, etc., so depending on your application it might be what you want.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530649</id>
	<title>Copy back</title>
	<author>duanes1967</author>
	<datestamp>1246384380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I too, am a bit surprised that FTP is failing.  It has been my experience that if there are network problems the transfer may slow to a crawl, but unless the network is dropping 10\% of the packets, I would be surprised if it failed.

Have you tried FTPing the same file back and see if there is really stuff missing, or if it is just technical differences in storage of the file?

As an aside - some of the old modem protocols might work for this.  The problem is likely the microwave connection coming and going.  I have seen MW drop in and out - it's madening.  FTP will definitely fail in that scenario.  You could also write your own little protocol that breaks the file into small pieces and transfers a chunk at a time and wait for an ack checksum.  If the connection is interupted, automatically stop and try to reconnect - then resume.  You're reinventing the wheel, but then you know exactly how the process works.</htmltext>
<tokenext>I too , am a bit surprised that FTP is failing .
It has been my experience that if there are network problems the transfer may slow to a crawl , but unless the network is dropping 10 \ % of the packets , I would be surprised if it failed .
Have you tried FTPing the same file back and see if there is really stuff missing , or if it is just technical differences in storage of the file ?
As an aside - some of the old modem protocols might work for this .
The problem is likely the microwave connection coming and going .
I have seen MW drop in and out - it 's madening .
FTP will definitely fail in that scenario .
You could also write your own little protocol that breaks the file into small pieces and transfers a chunk at a time and wait for an ack checksum .
If the connection is interupted , automatically stop and try to reconnect - then resume .
You 're reinventing the wheel , but then you know exactly how the process works .</tokentext>
<sentencetext>I too, am a bit surprised that FTP is failing.
It has been my experience that if there are network problems the transfer may slow to a crawl, but unless the network is dropping 10\% of the packets, I would be surprised if it failed.
Have you tried FTPing the same file back and see if there is really stuff missing, or if it is just technical differences in storage of the file?
As an aside - some of the old modem protocols might work for this.
The problem is likely the microwave connection coming and going.
I have seen MW drop in and out - it's madening.
FTP will definitely fail in that scenario.
You could also write your own little protocol that breaks the file into small pieces and transfers a chunk at a time and wait for an ack checksum.
If the connection is interupted, automatically stop and try to reconnect - then resume.
You're reinventing the wheel, but then you know exactly how the process works.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530269</id>
	<title>Well...duh</title>
	<author>alexborges</author>
	<datestamp>1246383420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Rsync over ssh and then a script to md5 at source and destination.</p><p>The last part may be tricky and/or slow depending on your filesize, but it will do the job for free.</p></htmltext>
<tokenext>Rsync over ssh and then a script to md5 at source and destination.The last part may be tricky and/or slow depending on your filesize , but it will do the job for free .</tokentext>
<sentencetext>Rsync over ssh and then a script to md5 at source and destination.The last part may be tricky and/or slow depending on your filesize, but it will do the job for free.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531075</id>
	<title>Kermit?</title>
	<author>LWATCDR</author>
	<datestamp>1246385400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><a href="http://www.columbia.edu/kermit/" title="columbia.edu">http://www.columbia.edu/kermit/</a> [columbia.edu]</p><p>It was designed to work under the worst conditions and with any type of machine on the planet.<br>It is old but still in use so it probably works really well.</p></htmltext>
<tokenext>http : //www.columbia.edu/kermit/ [ columbia.edu ] It was designed to work under the worst conditions and with any type of machine on the planet.It is old but still in use so it probably works really well .</tokentext>
<sentencetext>http://www.columbia.edu/kermit/ [columbia.edu]It was designed to work under the worst conditions and with any type of machine on the planet.It is old but still in use so it probably works really well.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532941</id>
	<title>Servers in either or both ends?</title>
	<author>Anonymous</author>
	<datestamp>1246391700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>How about Microsoft Data Protection Manager?<br>It was part of Windows 2003 R2, and thus probably requires a server in each end.<br>I guess you're able to run it atop an SSL connection or encrypted in some other way.<br>If you're worried about encryption you might want to make an IPSEC tunnel between the two nodes, then you can use whatever you want inside that tunnel.</p><p>It's been moved to System Center - http://www.microsoft.com/systemcenter/dataprotectionmanager/en/us/default.aspx - which might require other licenses than for Windows 2003 R2.</p><p>Also, BitTorrents, as suggested elsewhere, would be a possibility.<br>Only you need to ensure that you can reliably transfer the<nobr> <wbr></nobr>.torrent files first....</p><p>But if I were to choose I'd probably suggest using DFS replication since it's very simple - afaik it was improved in Windows 2003 R2 to be block based instead of file based, but I might be wrong on this....</p></htmltext>
<tokenext>How about Microsoft Data Protection Manager ? It was part of Windows 2003 R2 , and thus probably requires a server in each end.I guess you 're able to run it atop an SSL connection or encrypted in some other way.If you 're worried about encryption you might want to make an IPSEC tunnel between the two nodes , then you can use whatever you want inside that tunnel.It 's been moved to System Center - http : //www.microsoft.com/systemcenter/dataprotectionmanager/en/us/default.aspx - which might require other licenses than for Windows 2003 R2.Also , BitTorrents , as suggested elsewhere , would be a possibility.Only you need to ensure that you can reliably transfer the .torrent files first....But if I were to choose I 'd probably suggest using DFS replication since it 's very simple - afaik it was improved in Windows 2003 R2 to be block based instead of file based , but I might be wrong on this... .</tokentext>
<sentencetext>How about Microsoft Data Protection Manager?It was part of Windows 2003 R2, and thus probably requires a server in each end.I guess you're able to run it atop an SSL connection or encrypted in some other way.If you're worried about encryption you might want to make an IPSEC tunnel between the two nodes, then you can use whatever you want inside that tunnel.It's been moved to System Center - http://www.microsoft.com/systemcenter/dataprotectionmanager/en/us/default.aspx - which might require other licenses than for Windows 2003 R2.Also, BitTorrents, as suggested elsewhere, would be a possibility.Only you need to ensure that you can reliably transfer the .torrent files first....But if I were to choose I'd probably suggest using DFS replication since it's very simple - afaik it was improved in Windows 2003 R2 to be block based instead of file based, but I might be wrong on this....</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530265</id>
	<title>RCP</title>
	<author>digitalunity</author>
	<datestamp>1246383420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>it's not just for Linux.</p></htmltext>
<tokenext>it 's not just for Linux .</tokentext>
<sentencetext>it's not just for Linux.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331</id>
	<title>Re:TCP?</title>
	<author>Zocalo</author>
	<datestamp>1246383540000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>The only times I've seen FTP report a successful file transfer and have a file discrepency is when a binary file has been transferred in ASCII mode and the CR/LF sequences are being swapped for just CRs, or visa versa.  Nothing wrong with the protocol, PEBKAC...</htmltext>
<tokenext>The only times I 've seen FTP report a successful file transfer and have a file discrepency is when a binary file has been transferred in ASCII mode and the CR/LF sequences are being swapped for just CRs , or visa versa .
Nothing wrong with the protocol , PEBKAC.. .</tokentext>
<sentencetext>The only times I've seen FTP report a successful file transfer and have a file discrepency is when a binary file has been transferred in ASCII mode and the CR/LF sequences are being swapped for just CRs, or visa versa.
Nothing wrong with the protocol, PEBKAC...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532737</id>
	<title>Re:PAR2?</title>
	<author>sexconker</author>
	<datestamp>1246390920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>We know the files are different.<br>We know Par2 will say the file needs to be repaired.<br>We need to know why.</p><p>We know why.  It's CR+LF, or a shitty FTP server/client.</p></htmltext>
<tokenext>We know the files are different.We know Par2 will say the file needs to be repaired.We need to know why.We know why .
It 's CR + LF , or a shitty FTP server/client .</tokentext>
<sentencetext>We know the files are different.We know Par2 will say the file needs to be repaired.We need to know why.We know why.
It's CR+LF, or a shitty FTP server/client.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531293</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539301</id>
	<title>Re:Any encrypted transmission protocol actually</title>
	<author>Anonymous</author>
	<datestamp>1246391640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I bet you are right.  These are government windows guys.</p><p>Here, use this to tell if it changed:<br><a href="http://downloads.activestate.com/contrib/md5sum/Windows/" title="activestate.com" rel="nofollow">md5sum</a> [activestate.com]</p></htmltext>
<tokenext>I bet you are right .
These are government windows guys.Here , use this to tell if it changed : md5sum [ activestate.com ]</tokentext>
<sentencetext>I bet you are right.
These are government windows guys.Here, use this to tell if it changed:md5sum [activestate.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535305</id>
	<title>Z-Modem FTW!</title>
	<author>Anonymous</author>
	<datestamp>1246359180000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>Crappy connection?  Resumable transfers?  Slow connections?  Sounds like the good old BBS days!
</p><p>
Z-modem is your answer.
</p></htmltext>
<tokenext>Crappy connection ?
Resumable transfers ?
Slow connections ?
Sounds like the good old BBS days !
Z-modem is your answer .</tokentext>
<sentencetext>Crappy connection?
Resumable transfers?
Slow connections?
Sounds like the good old BBS days!
Z-modem is your answer.
</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535683</id>
	<title>Re:You're kidding, aren't you??</title>
	<author>Anonymous</author>
	<datestamp>1246361160000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think this is a technical problem unless you are working using COVER YOUR ASS engineering.</p><p>You can start working under the assumption that a new line is cost prohibitive or impossible, (more expensive than a week of salary for a engineer, or maybe they are replacing the OS of the voyager 2). Also the problem sounds very simple so i don't understand why to make that much of a hassle.</p><p>Remember you are paid to solve problems, not to bitch about them.</p></htmltext>
<tokenext>I think this is a technical problem unless you are working using COVER YOUR ASS engineering.You can start working under the assumption that a new line is cost prohibitive or impossible , ( more expensive than a week of salary for a engineer , or maybe they are replacing the OS of the voyager 2 ) .
Also the problem sounds very simple so i do n't understand why to make that much of a hassle.Remember you are paid to solve problems , not to bitch about them .</tokentext>
<sentencetext>I think this is a technical problem unless you are working using COVER YOUR ASS engineering.You can start working under the assumption that a new line is cost prohibitive or impossible, (more expensive than a week of salary for a engineer, or maybe they are replacing the OS of the voyager 2).
Also the problem sounds very simple so i don't understand why to make that much of a hassle.Remember you are paid to solve problems, not to bitch about them.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534397</id>
	<title>Torrent?</title>
	<author>crowne</author>
	<datestamp>1246354620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'm sure the dodgy government network would love that....</htmltext>
<tokenext>I 'm sure the dodgy government network would love that... .</tokentext>
<sentencetext>I'm sure the dodgy government network would love that....</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531573</id>
	<title>Different FS cluster size on both ends?</title>
	<author>Anonymous</author>
	<datestamp>1246386900000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It would explain a difference in file size.</p></htmltext>
<tokenext>It would explain a difference in file size .</tokentext>
<sentencetext>It would explain a difference in file size.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539715</id>
	<title>I do this for a living</title>
	<author>Anonymous</author>
	<datestamp>1246440300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I been working at doing things like this for a living the last 9 years.</p><p>When you say Mission Critical and Corrupt Files in the same sentence I just had to reply.</p><p>There are a lot of firewalls and FTP clients that actually trashes FTP connections. It all depends on what you are using.<br>I would suggest that you either try to find out why the files get trashed. But if the files really are mission critical like you say<br>you need some way to make \_sure\_ they are transfered. It's called Transaction Safety.</p><p>If you can not figure out what's going wrong with your connections (why bytes are cut). Then you need to change protocol.<br>Changing it for a encrypted protocol might work, cause if the data in the transmissions gets trashed, the encryption would<br>also be trashed and the protocol would cancel the operation. Adding transaction safety to this, you would be resends when<br>things blowup. This should ensure you that your file passes though.</p><p>This feels like spam, and it is.. but.. it fits so good, I actually have to write it down for you:<br>Our product transfers data from machine to machine over different protocols in a transaction safe way.<br>It might be a bit overkill for what you are describing, but we general talk about Mediation to describe what you are trying to solve.</p><p>We can schedule transfers, over different protocols, with the ability to add business logic (translating data from one format to an other on the fly).<br>On top of my head, I think any of the following would work for you: FTP, SFTP, SCP (we also talk to webservices, x25, databases, etc.. )</p><p>If this sounds interesting, you contact us (digitalroute.com) for sales material.. but I do not have any<nobr> <wbr></nobr>:-) I'm just a developer here.<nobr> <wbr></nobr>/Kristoffer</p></htmltext>
<tokenext>I been working at doing things like this for a living the last 9 years.When you say Mission Critical and Corrupt Files in the same sentence I just had to reply.There are a lot of firewalls and FTP clients that actually trashes FTP connections .
It all depends on what you are using.I would suggest that you either try to find out why the files get trashed .
But if the files really are mission critical like you sayyou need some way to make \ _sure \ _ they are transfered .
It 's called Transaction Safety.If you can not figure out what 's going wrong with your connections ( why bytes are cut ) .
Then you need to change protocol.Changing it for a encrypted protocol might work , cause if the data in the transmissions gets trashed , the encryption wouldalso be trashed and the protocol would cancel the operation .
Adding transaction safety to this , you would be resends whenthings blowup .
This should ensure you that your file passes though.This feels like spam , and it is.. but.. it fits so good , I actually have to write it down for you : Our product transfers data from machine to machine over different protocols in a transaction safe way.It might be a bit overkill for what you are describing , but we general talk about Mediation to describe what you are trying to solve.We can schedule transfers , over different protocols , with the ability to add business logic ( translating data from one format to an other on the fly ) .On top of my head , I think any of the following would work for you : FTP , SFTP , SCP ( we also talk to webservices , x25 , databases , etc.. ) If this sounds interesting , you contact us ( digitalroute.com ) for sales material.. but I do not have any : - ) I 'm just a developer here .
/Kristoffer</tokentext>
<sentencetext>I been working at doing things like this for a living the last 9 years.When you say Mission Critical and Corrupt Files in the same sentence I just had to reply.There are a lot of firewalls and FTP clients that actually trashes FTP connections.
It all depends on what you are using.I would suggest that you either try to find out why the files get trashed.
But if the files really are mission critical like you sayyou need some way to make \_sure\_ they are transfered.
It's called Transaction Safety.If you can not figure out what's going wrong with your connections (why bytes are cut).
Then you need to change protocol.Changing it for a encrypted protocol might work, cause if the data in the transmissions gets trashed, the encryption wouldalso be trashed and the protocol would cancel the operation.
Adding transaction safety to this, you would be resends whenthings blowup.
This should ensure you that your file passes though.This feels like spam, and it is.. but.. it fits so good, I actually have to write it down for you:Our product transfers data from machine to machine over different protocols in a transaction safe way.It might be a bit overkill for what you are describing, but we general talk about Mediation to describe what you are trying to solve.We can schedule transfers, over different protocols, with the ability to add business logic (translating data from one format to an other on the fly).On top of my head, I think any of the following would work for you: FTP, SFTP, SCP (we also talk to webservices, x25, databases, etc.. )If this sounds interesting, you contact us (digitalroute.com) for sales material.. but I do not have any :-) I'm just a developer here.
/Kristoffer</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530445</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246383840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>TCP is as reliable as borrowing a brand new Ferrari to the crack dealer on the street corner.</p><p>UDP of course, is less reliable than that. The Ferrari is rigged with a bomb.</p></htmltext>
<tokenext>TCP is as reliable as borrowing a brand new Ferrari to the crack dealer on the street corner.UDP of course , is less reliable than that .
The Ferrari is rigged with a bomb .</tokentext>
<sentencetext>TCP is as reliable as borrowing a brand new Ferrari to the crack dealer on the street corner.UDP of course, is less reliable than that.
The Ferrari is rigged with a bomb.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533361</id>
	<title>If Windows on both ends, please use SyncToy 2.0</title>
	<author>Anonymous</author>
	<datestamp>1246393620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>It uses the Microsoft Sync Framework - we've been using it for database backups for months and *love* it.  You just install, set up your source/dest folders through the UI, then run them.  For doing so on a schedule, just add a scheduled task for SyncToyCmd.exe -R</p><p><a href="http://en.wikipedia.org/wiki/SyncToy" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/SyncToy</a> [wikipedia.org]<br><a href="http://www.microsoft.com/downloads/details.aspx?familyid=c26efa36-98e0-4ee9-a7c5-98d0592d8c52&amp;displaylang=en" title="microsoft.com" rel="nofollow">http://www.microsoft.com/downloads/details.aspx?familyid=c26efa36-98e0-4ee9-a7c5-98d0592d8c52&amp;displaylang=en</a> [microsoft.com]<br><a href="http://en.wikipedia.org/wiki/Microsoft\_Sync\_Framework" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Microsoft\_Sync\_Framework</a> [wikipedia.org]</p><p>If you just wanted "copy with retries" you could go with something simpler like Robocopy, but I think you'll be quite happy with SyncToy!</p><p><a href="http://en.wikipedia.org/wiki/Robocopy" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Robocopy</a> [wikipedia.org]</p></htmltext>
<tokenext>It uses the Microsoft Sync Framework - we 've been using it for database backups for months and * love * it .
You just install , set up your source/dest folders through the UI , then run them .
For doing so on a schedule , just add a scheduled task for SyncToyCmd.exe -Rhttp : //en.wikipedia.org/wiki/SyncToy [ wikipedia.org ] http : //www.microsoft.com/downloads/details.aspx ? familyid = c26efa36-98e0-4ee9-a7c5-98d0592d8c52&amp;displaylang = en [ microsoft.com ] http : //en.wikipedia.org/wiki/Microsoft \ _Sync \ _Framework [ wikipedia.org ] If you just wanted " copy with retries " you could go with something simpler like Robocopy , but I think you 'll be quite happy with SyncToy ! http : //en.wikipedia.org/wiki/Robocopy [ wikipedia.org ]</tokentext>
<sentencetext>It uses the Microsoft Sync Framework - we've been using it for database backups for months and *love* it.
You just install, set up your source/dest folders through the UI, then run them.
For doing so on a schedule, just add a scheduled task for SyncToyCmd.exe -Rhttp://en.wikipedia.org/wiki/SyncToy [wikipedia.org]http://www.microsoft.com/downloads/details.aspx?familyid=c26efa36-98e0-4ee9-a7c5-98d0592d8c52&amp;displaylang=en [microsoft.com]http://en.wikipedia.org/wiki/Microsoft\_Sync\_Framework [wikipedia.org]If you just wanted "copy with retries" you could go with something simpler like Robocopy, but I think you'll be quite happy with SyncToy!http://en.wikipedia.org/wiki/Robocopy [wikipedia.org]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530961</id>
	<title>MOD PARENT UP</title>
	<author>inject\_hotmail.com</author>
	<datestamp>1246385100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Parent is 100\% accurate.  This is integral to binary file transmission via FTP.  Transfer mode (binary or text) may be set to text on the server by default.  Without the proper setting, things won't transfer properly.<p>
'hash' is also a nice feature...</p></htmltext>
<tokenext>Parent is 100 \ % accurate .
This is integral to binary file transmission via FTP .
Transfer mode ( binary or text ) may be set to text on the server by default .
Without the proper setting , things wo n't transfer properly .
'hash ' is also a nice feature.. .</tokentext>
<sentencetext>Parent is 100\% accurate.
This is integral to binary file transmission via FTP.
Transfer mode (binary or text) may be set to text on the server by default.
Without the proper setting, things won't transfer properly.
'hash' is also a nice feature...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533887</id>
	<title>Re:TCP?</title>
	<author>Obfuscant</author>
	<datestamp>1246352700000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><i>As far as I can tell, the problem is entirely unique to notepad. </i> <p>
Who rated this "insightful"?</p><p>
I'm sorry, but I've worked in this area for years. I was responsible for moving data and source files to and from Unix to DOS to VMS to OSs that are even deader than VMS, and the problem is hardly unique to "notepad". YOU may see it only in notepad because YOU only use Windows, but there are a lot of other OSs out there. If you've never worked on an OS that has structured files inherent in the filesystem, well, lucky you. I have. The newlines in those kinds of files are completely lost when you copy the byte stream contents, because the newlines are implicit and defined in the file structure itself. A fixed-record file doesn't need newlines because every line is the same length.</p><p>
<i>Every other text editor I've ever tried handles files with Unix-style newlines correctly.</i> </p><p>
There is much more to the world than Windows and Unix-style newlines. If all you have seen is Windows and Unix newlines, I suppose you could think the problem was limited to that, but it really isn't. In fact, if you use FTP much at all, I suspect even you have been protected by ASCII mode, to the point that you never even knew that an FTP site you visited was VMS-based. I know I've been to VMS sites, and ASCII mode is critical if you are dealing with ASCII files.</p></htmltext>
<tokenext>As far as I can tell , the problem is entirely unique to notepad .
Who rated this " insightful " ?
I 'm sorry , but I 've worked in this area for years .
I was responsible for moving data and source files to and from Unix to DOS to VMS to OSs that are even deader than VMS , and the problem is hardly unique to " notepad " .
YOU may see it only in notepad because YOU only use Windows , but there are a lot of other OSs out there .
If you 've never worked on an OS that has structured files inherent in the filesystem , well , lucky you .
I have .
The newlines in those kinds of files are completely lost when you copy the byte stream contents , because the newlines are implicit and defined in the file structure itself .
A fixed-record file does n't need newlines because every line is the same length .
Every other text editor I 've ever tried handles files with Unix-style newlines correctly .
There is much more to the world than Windows and Unix-style newlines .
If all you have seen is Windows and Unix newlines , I suppose you could think the problem was limited to that , but it really is n't .
In fact , if you use FTP much at all , I suspect even you have been protected by ASCII mode , to the point that you never even knew that an FTP site you visited was VMS-based .
I know I 've been to VMS sites , and ASCII mode is critical if you are dealing with ASCII files .</tokentext>
<sentencetext>As far as I can tell, the problem is entirely unique to notepad.
Who rated this "insightful"?
I'm sorry, but I've worked in this area for years.
I was responsible for moving data and source files to and from Unix to DOS to VMS to OSs that are even deader than VMS, and the problem is hardly unique to "notepad".
YOU may see it only in notepad because YOU only use Windows, but there are a lot of other OSs out there.
If you've never worked on an OS that has structured files inherent in the filesystem, well, lucky you.
I have.
The newlines in those kinds of files are completely lost when you copy the byte stream contents, because the newlines are implicit and defined in the file structure itself.
A fixed-record file doesn't need newlines because every line is the same length.
Every other text editor I've ever tried handles files with Unix-style newlines correctly.
There is much more to the world than Windows and Unix-style newlines.
If all you have seen is Windows and Unix newlines, I suppose you could think the problem was limited to that, but it really isn't.
In fact, if you use FTP much at all, I suspect even you have been protected by ASCII mode, to the point that you never even knew that an FTP site you visited was VMS-based.
I know I've been to VMS sites, and ASCII mode is critical if you are dealing with ASCII files.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533487</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531951</id>
	<title>Quickpar...</title>
	<author>CrackerJackz</author>
	<datestamp>1246388220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you have access to the file at the remote end I would run it though QuickPar <a href="http://www.quickpar.org.uk/" title="quickpar.org.uk" rel="nofollow">http://www.quickpar.org.uk/</a> [quickpar.org.uk] at that point you can split the file into a group of smaller files (less chance of any one file being mangled), plus add ckecksum files to the set, that way if one of the files is mangled in transport it's 1: identifiable and 2. automatically fixed by reassembling the par files on your end of the connection.</p></htmltext>
<tokenext>If you have access to the file at the remote end I would run it though QuickPar http : //www.quickpar.org.uk/ [ quickpar.org.uk ] at that point you can split the file into a group of smaller files ( less chance of any one file being mangled ) , plus add ckecksum files to the set , that way if one of the files is mangled in transport it 's 1 : identifiable and 2. automatically fixed by reassembling the par files on your end of the connection .</tokentext>
<sentencetext>If you have access to the file at the remote end I would run it though QuickPar http://www.quickpar.org.uk/ [quickpar.org.uk] at that point you can split the file into a group of smaller files (less chance of any one file being mangled), plus add ckecksum files to the set, that way if one of the files is mangled in transport it's 1: identifiable and 2. automatically fixed by reassembling the par files on your end of the connection.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530653</id>
	<title>RSync would do the trick nicely</title>
	<author>Anonymous</author>
	<datestamp>1246384380000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>Why don't you try rsync. That should do the trick nicely.</p></htmltext>
<tokenext>Why do n't you try rsync .
That should do the trick nicely .</tokentext>
<sentencetext>Why don't you try rsync.
That should do the trick nicely.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536867</id>
	<title>Re:Line endings!</title>
	<author>Anonymous</author>
	<datestamp>1246367760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>\n\r is mac<br>\r\n is windows<br>\n is unix/linux</p></htmltext>
<tokenext>\ n \ r is mac \ r \ n is windows \ n is unix/linux</tokentext>
<sentencetext>\n\r is mac\r\n is windows\n is unix/linux</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530755</id>
	<title>MULE</title>
	<author>Anonymous</author>
	<datestamp>1246384680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>http://www.mulesource.org/display/MULE/Home</p><p>Using it purely as a file transport is a bit like using a sledgehammer to open a walnut, but it will do the job and do it well.</p></htmltext>
<tokenext>http : //www.mulesource.org/display/MULE/HomeUsing it purely as a file transport is a bit like using a sledgehammer to open a walnut , but it will do the job and do it well .</tokentext>
<sentencetext>http://www.mulesource.org/display/MULE/HomeUsing it purely as a file transport is a bit like using a sledgehammer to open a walnut, but it will do the job and do it well.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530971</id>
	<title>SQL Server Service Broker</title>
	<author>JKDguy82</author>
	<datestamp>1246385160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If you are also utilizing SQL Server (2005/2008), one option would be Service Broker, as it has guaranteed message delivery. And as long as at least one of the endpoints is using the Standard Edition or better, the rest can use the free express version.</htmltext>
<tokenext>If you are also utilizing SQL Server ( 2005/2008 ) , one option would be Service Broker , as it has guaranteed message delivery .
And as long as at least one of the endpoints is using the Standard Edition or better , the rest can use the free express version .</tokentext>
<sentencetext>If you are also utilizing SQL Server (2005/2008), one option would be Service Broker, as it has guaranteed message delivery.
And as long as at least one of the endpoints is using the Standard Edition or better, the rest can use the free express version.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539803</id>
	<title>You're still discussing this?</title>
	<author>Anonymous</author>
	<datestamp>1246441800000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Fer christs sake!<br>WinSCP using either SCP or SFTP protocol. End of story. Can't believe this is being asked.</p></htmltext>
<tokenext>Fer christs sake ! WinSCP using either SCP or SFTP protocol .
End of story .
Ca n't believe this is being asked .</tokentext>
<sentencetext>Fer christs sake!WinSCP using either SCP or SFTP protocol.
End of story.
Can't believe this is being asked.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536853</id>
	<title>Re:TCP?</title>
	<author>gTsiros</author>
	<datestamp>1246367580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>quick to stamp 'ignorant' on someone, aren't we?</p><p>taking other posts into consideration i'd say you've lost the bet.</p></htmltext>
<tokenext>quick to stamp 'ignorant ' on someone , are n't we ? taking other posts into consideration i 'd say you 've lost the bet .</tokentext>
<sentencetext>quick to stamp 'ignorant' on someone, aren't we?taking other posts into consideration i'd say you've lost the bet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532741</id>
	<title>Re:UDP.</title>
	<author>interval1066</author>
	<datestamp>1246390920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>UDP? I thought the idea was "guaranteed" data transmission.</htmltext>
<tokenext>UDP ?
I thought the idea was " guaranteed " data transmission .</tokentext>
<sentencetext>UDP?
I thought the idea was "guaranteed" data transmission.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135</id>
	<title>UDP.</title>
	<author>Anonymous</author>
	<datestamp>1246383120000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>Clearly you're looking for UDP. Next question.</htmltext>
<tokenext>Clearly you 're looking for UDP .
Next question .</tokentext>
<sentencetext>Clearly you're looking for UDP.
Next question.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532259</id>
	<title>Some sorta bittorrent-esque app over tcp/ip</title>
	<author>jameskojiro</author>
	<datestamp>1246389240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>With some sort of CRC checking going on...</p></htmltext>
<tokenext>With some sort of CRC checking going on.. .</tokentext>
<sentencetext>With some sort of CRC checking going on...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536691</id>
	<title>Re:Any encrypted transmission protocol actually</title>
	<author>complete loony</author>
	<datestamp>1246366560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Actually missing the last packet or two of a TCP stream is common if you shutdown the stream incorrectly. I ran into this problem when I tried to write an ftp client on windows. My guess is either their ftp client / server has a bug or the unreliable network he talks about is causing enough dropped packets to abort the connection early and their download client is not retrying.
</p><p>So my recommendation would be to use some kind of download manager that can open multiple streams, that will retry on any connection failure, and ideally a protocol that does end to end checksums of the whole file to ensure it downloaded correctly.</p></htmltext>
<tokenext>Actually missing the last packet or two of a TCP stream is common if you shutdown the stream incorrectly .
I ran into this problem when I tried to write an ftp client on windows .
My guess is either their ftp client / server has a bug or the unreliable network he talks about is causing enough dropped packets to abort the connection early and their download client is not retrying .
So my recommendation would be to use some kind of download manager that can open multiple streams , that will retry on any connection failure , and ideally a protocol that does end to end checksums of the whole file to ensure it downloaded correctly .</tokentext>
<sentencetext>Actually missing the last packet or two of a TCP stream is common if you shutdown the stream incorrectly.
I ran into this problem when I tried to write an ftp client on windows.
My guess is either their ftp client / server has a bug or the unreliable network he talks about is causing enough dropped packets to abort the connection early and their download client is not retrying.
So my recommendation would be to use some kind of download manager that can open multiple streams, that will retry on any connection failure, and ideally a protocol that does end to end checksums of the whole file to ensure it downloaded correctly.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533223</id>
	<title>Re:RTFM - set binary mode in FTP</title>
	<author>RomulusNR</author>
	<datestamp>1246392900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yeah, this post seemed like a practice network admin (or sysadmin, or qa) question. Large files, losing a few KB after ftp, why would that happen?</p><p>The OP doesn't say exactly in what way the FTP files were affected except that they were smaller -- not that there was any actual identifiable data missing.</p></htmltext>
<tokenext>Yeah , this post seemed like a practice network admin ( or sysadmin , or qa ) question .
Large files , losing a few KB after ftp , why would that happen ? The OP does n't say exactly in what way the FTP files were affected except that they were smaller -- not that there was any actual identifiable data missing .</tokentext>
<sentencetext>Yeah, this post seemed like a practice network admin (or sysadmin, or qa) question.
Large files, losing a few KB after ftp, why would that happen?The OP doesn't say exactly in what way the FTP files were affected except that they were smaller -- not that there was any actual identifiable data missing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531271</id>
	<title>I seem to recall...</title>
	<author>cshark</author>
	<datestamp>1246386000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>that this is an issue with the size of your hash... I think.<br>Check the message boards for documentation. Others have had this same issue.<br>It's not FTP that's the problem. It's the implementation. Try others.</p><p>Switching to a new protocol, especially one like UDP that has no built in error correction is going to be complicated and costly.<br>Especially if you can fix the issue with FTP; which, I think you can.</p></htmltext>
<tokenext>that this is an issue with the size of your hash... I think.Check the message boards for documentation .
Others have had this same issue.It 's not FTP that 's the problem .
It 's the implementation .
Try others.Switching to a new protocol , especially one like UDP that has no built in error correction is going to be complicated and costly.Especially if you can fix the issue with FTP ; which , I think you can .</tokentext>
<sentencetext>that this is an issue with the size of your hash... I think.Check the message boards for documentation.
Others have had this same issue.It's not FTP that's the problem.
It's the implementation.
Try others.Switching to a new protocol, especially one like UDP that has no built in error correction is going to be complicated and costly.Especially if you can fix the issue with FTP; which, I think you can.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532153</id>
	<title>Set BINARY MODE in FTP!!!</title>
	<author>Anonymous</author>
	<datestamp>1246388820000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>FTP and TCP cannot "Drop" packets or bytes.  You need to learn-up on TCP and FTP.</p><p>FTP \_does\_ translate DOS end-of-line sequences (carriage-return followed by new-line -- 2 bytes) with Unix end-of-line sequences (just new-line -- 1 byte).  So your files may become shorter by as many bytes as they contain lines.</p><p>The solution is to tell FTP to not treat the file as text, but as binary image information in which new-line characters are treated with no special processing.  Traditionally, FTP called this "file type I" and the command to set it is "bin" as in "binary":</p><p><tt><br>C:\Documents and Settings\fred&gt;ftp abc.net<br>Connected to abc.net.<br>220 ProFTPD 1.3.1 Server (ABC Global Enterprise Group) [10.13.131.34]<br>User (abc.net:(none)): freddy<br>331 Password required for freddy<br>Password:<br>230 User freddy logged in<br>ftp&gt; <b>bin</b><br><b> <i>200 Type set to I</i> </b><br>ftp&gt;<br></tt></p></htmltext>
<tokenext>FTP and TCP can not " Drop " packets or bytes .
You need to learn-up on TCP and FTP.FTP \ _does \ _ translate DOS end-of-line sequences ( carriage-return followed by new-line -- 2 bytes ) with Unix end-of-line sequences ( just new-line -- 1 byte ) .
So your files may become shorter by as many bytes as they contain lines.The solution is to tell FTP to not treat the file as text , but as binary image information in which new-line characters are treated with no special processing .
Traditionally , FTP called this " file type I " and the command to set it is " bin " as in " binary " : C : \ Documents and Settings \ fred &gt; ftp abc.netConnected to abc.net.220 ProFTPD 1.3.1 Server ( ABC Global Enterprise Group ) [ 10.13.131.34 ] User ( abc.net : ( none ) ) : freddy331 Password required for freddyPassword : 230 User freddy logged inftp &gt; bin 200 Type set to I ftp &gt;</tokentext>
<sentencetext>FTP and TCP cannot "Drop" packets or bytes.
You need to learn-up on TCP and FTP.FTP \_does\_ translate DOS end-of-line sequences (carriage-return followed by new-line -- 2 bytes) with Unix end-of-line sequences (just new-line -- 1 byte).
So your files may become shorter by as many bytes as they contain lines.The solution is to tell FTP to not treat the file as text, but as binary image information in which new-line characters are treated with no special processing.
Traditionally, FTP called this "file type I" and the command to set it is "bin" as in "binary":C:\Documents and Settings\fred&gt;ftp abc.netConnected to abc.net.220 ProFTPD 1.3.1 Server (ABC Global Enterprise Group) [10.13.131.34]User (abc.net:(none)): freddy331 Password required for freddyPassword:230 User freddy logged inftp&gt; bin 200 Type set to I ftp&gt;</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531799</id>
	<title>Re:Correct me if I'm wrong...</title>
	<author>natoochtoniket</author>
	<datestamp>1246387620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yes.  TCP was/is designed to detect and correct data transmission errors.  The information coding is highly redundant, and the error correction and detection is implemented in each of several layers.  (See, <a href="http://www.faqs.org/rfcs/rfc793.html" title="faqs.org">http://www.faqs.org/rfcs/rfc793.html</a> [faqs.org] ).  The probability of an undetected error is very small.  The datalink layer in most networks typically provide an undetected error rate in the neighborhood of 2^-32.  Then the upper layer tcp does another layer of error coding, providing a combined error rate of something like 2^-64.  That is fine for most practical purposes.</p><p>You can improve on the available error detection if you want, by computing a checksum of the file, transmitting both the file and the checksum, and then recomputing and comparing the checksum on the receiving end.  Various algorithms are available for such a purpose.  Two good hash algorithms that comes to mind are MD5 and SHA-1.  (See, <a href="http://en.wikipedia.org/wiki/Comparison\_of\_cryptographic\_hash\_functions" title="wikipedia.org">http://en.wikipedia.org/wiki/Comparison\_of\_cryptographic\_hash\_functions</a> [wikipedia.org] ).</p></htmltext>
<tokenext>Yes .
TCP was/is designed to detect and correct data transmission errors .
The information coding is highly redundant , and the error correction and detection is implemented in each of several layers .
( See , http : //www.faqs.org/rfcs/rfc793.html [ faqs.org ] ) .
The probability of an undetected error is very small .
The datalink layer in most networks typically provide an undetected error rate in the neighborhood of 2 ^ -32 .
Then the upper layer tcp does another layer of error coding , providing a combined error rate of something like 2 ^ -64 .
That is fine for most practical purposes.You can improve on the available error detection if you want , by computing a checksum of the file , transmitting both the file and the checksum , and then recomputing and comparing the checksum on the receiving end .
Various algorithms are available for such a purpose .
Two good hash algorithms that comes to mind are MD5 and SHA-1 .
( See , http : //en.wikipedia.org/wiki/Comparison \ _of \ _cryptographic \ _hash \ _functions [ wikipedia.org ] ) .</tokentext>
<sentencetext>Yes.
TCP was/is designed to detect and correct data transmission errors.
The information coding is highly redundant, and the error correction and detection is implemented in each of several layers.
(See, http://www.faqs.org/rfcs/rfc793.html [faqs.org] ).
The probability of an undetected error is very small.
The datalink layer in most networks typically provide an undetected error rate in the neighborhood of 2^-32.
Then the upper layer tcp does another layer of error coding, providing a combined error rate of something like 2^-64.
That is fine for most practical purposes.You can improve on the available error detection if you want, by computing a checksum of the file, transmitting both the file and the checksum, and then recomputing and comparing the checksum on the receiving end.
Various algorithms are available for such a purpose.
Two good hash algorithms that comes to mind are MD5 and SHA-1.
(See, http://en.wikipedia.org/wiki/Comparison\_of\_cryptographic\_hash\_functions [wikipedia.org] ).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535473</id>
	<title>Re:TCP?</title>
	<author>Nefarious Wheel</author>
	<datestamp>1246360080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>IBM's MQ Series is indeed bulletproof.  Guaranteed single-instance delivery.  Runs on everything from mainframes to a chip nailed to a block of wood.<p>Another option would be the FileZilla client perhaps.  Install XAMPP on your Windows box for a very nice WAMP environment. I use it for a Joomla! instance and it comes with FileZilla.  No problems with it to date.</p></htmltext>
<tokenext>IBM 's MQ Series is indeed bulletproof .
Guaranteed single-instance delivery .
Runs on everything from mainframes to a chip nailed to a block of wood.Another option would be the FileZilla client perhaps .
Install XAMPP on your Windows box for a very nice WAMP environment .
I use it for a Joomla !
instance and it comes with FileZilla .
No problems with it to date .</tokentext>
<sentencetext>IBM's MQ Series is indeed bulletproof.
Guaranteed single-instance delivery.
Runs on everything from mainframes to a chip nailed to a block of wood.Another option would be the FileZilla client perhaps.
Install XAMPP on your Windows box for a very nice WAMP environment.
I use it for a Joomla!
instance and it comes with FileZilla.
No problems with it to date.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531239</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530933</id>
	<title>Re:Correct me if I'm wrong...</title>
	<author>duanes1967</author>
	<datestamp>1246385040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>If the connection is truly crappy, FTP will certainly stall and get closed by the firewall or NAT.</htmltext>
<tokenext>If the connection is truly crappy , FTP will certainly stall and get closed by the firewall or NAT .</tokentext>
<sentencetext>If the connection is truly crappy, FTP will certainly stall and get closed by the firewall or NAT.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533487</id>
	<title>Re:TCP?</title>
	<author>Jimmy\_B</author>
	<datestamp>1246394220000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p>Not if you have an "ASCII" file you are trying to read on Windows that has Unix newline conventions. Try opening a newlined file with notepad, for example.</p></div></blockquote><p>
As far as I can tell, the problem is entirely unique to notepad. Every other text editor I've ever tried handles files with Unix-style newlines correctly. Since it would be trivial to fix Notepad, I can only assume that Microsoft either doesn't care at all about Notepad, or is deliberately leaving the incompatibility in place to discourage use of Unix.</p></div>
	</htmltext>
<tokenext>Not if you have an " ASCII " file you are trying to read on Windows that has Unix newline conventions .
Try opening a newlined file with notepad , for example .
As far as I can tell , the problem is entirely unique to notepad .
Every other text editor I 've ever tried handles files with Unix-style newlines correctly .
Since it would be trivial to fix Notepad , I can only assume that Microsoft either does n't care at all about Notepad , or is deliberately leaving the incompatibility in place to discourage use of Unix .</tokentext>
<sentencetext>Not if you have an "ASCII" file you are trying to read on Windows that has Unix newline conventions.
Try opening a newlined file with notepad, for example.
As far as I can tell, the problem is entirely unique to notepad.
Every other text editor I've ever tried handles files with Unix-style newlines correctly.
Since it would be trivial to fix Notepad, I can only assume that Microsoft either doesn't care at all about Notepad, or is deliberately leaving the incompatibility in place to discourage use of Unix.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28537979</id>
	<title>Re:TCP?</title>
	<author>Anonymous</author>
	<datestamp>1246376820000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This kind of reasoning is ridiculous. It's File Transport Protocol, not File Conversion Protocol.<br>Should FTP now be expected to convert files that are little-endian to big-endian format? Office 2003 to 2007? MPEG2 to H.264?</p></htmltext>
<tokenext>This kind of reasoning is ridiculous .
It 's File Transport Protocol , not File Conversion Protocol.Should FTP now be expected to convert files that are little-endian to big-endian format ?
Office 2003 to 2007 ?
MPEG2 to H.264 ?</tokentext>
<sentencetext>This kind of reasoning is ridiculous.
It's File Transport Protocol, not File Conversion Protocol.Should FTP now be expected to convert files that are little-endian to big-endian format?
Office 2003 to 2007?
MPEG2 to H.264?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531531</id>
	<title>Couple options.</title>
	<author>Psyko</author>
	<datestamp>1246386720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If you're stuck on windows, have no control of the link, need to guarantee delivery, need encryption options, are stuck in specific delivery timeframes, and need it scriptable with triggering etc. there's quite a few commercial options.</p><p>The 2 I've used the most are the following:</p><p>Aspera FASP - <a href="http://www.asperasoft.com/" title="asperasoft.com" rel="nofollow">http://www.asperasoft.com/</a> [asperasoft.com]<br>Sterling Connect:Direct <a href="http://www.sterlingcommerce.com/products/managed-file-transfer/connect-direct/" title="sterlingcommerce.com" rel="nofollow">http://www.sterlingcommerce.com/products/managed-file-transfer/connect-direct/</a> [sterlingcommerce.com]</p><p>Connect direct is geared more towards highly distributed delivery channels, where you've got lots of ingress/egress points to different locations (think multi site, multi customer distribution) so it could be a bit overkill, but aspera is great at utilizing a link to it's peak (it'll udp flood a pipe and guarantee delivery), in fact if you don't watch what you're doing you can pretty much storm everyone else off the link, but your data will get there &gt;;)</p></htmltext>
<tokenext>If you 're stuck on windows , have no control of the link , need to guarantee delivery , need encryption options , are stuck in specific delivery timeframes , and need it scriptable with triggering etc .
there 's quite a few commercial options.The 2 I 've used the most are the following : Aspera FASP - http : //www.asperasoft.com/ [ asperasoft.com ] Sterling Connect : Direct http : //www.sterlingcommerce.com/products/managed-file-transfer/connect-direct/ [ sterlingcommerce.com ] Connect direct is geared more towards highly distributed delivery channels , where you 've got lots of ingress/egress points to different locations ( think multi site , multi customer distribution ) so it could be a bit overkill , but aspera is great at utilizing a link to it 's peak ( it 'll udp flood a pipe and guarantee delivery ) , in fact if you do n't watch what you 're doing you can pretty much storm everyone else off the link , but your data will get there &gt; ; )</tokentext>
<sentencetext>If you're stuck on windows, have no control of the link, need to guarantee delivery, need encryption options, are stuck in specific delivery timeframes, and need it scriptable with triggering etc.
there's quite a few commercial options.The 2 I've used the most are the following:Aspera FASP - http://www.asperasoft.com/ [asperasoft.com]Sterling Connect:Direct http://www.sterlingcommerce.com/products/managed-file-transfer/connect-direct/ [sterlingcommerce.com]Connect direct is geared more towards highly distributed delivery channels, where you've got lots of ingress/egress points to different locations (think multi site, multi customer distribution) so it could be a bit overkill, but aspera is great at utilizing a link to it's peak (it'll udp flood a pipe and guarantee delivery), in fact if you don't watch what you're doing you can pretty much storm everyone else off the link, but your data will get there &gt;;)</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_65</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531043
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531293
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532737
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_72</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539301
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530645
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_87</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530525
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533281
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530279
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532169
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_92</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531997
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_94</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533477
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_73</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28537979
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_64</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536267
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530711
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530279
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531719
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531799
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531571
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532113
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533485
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533339
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_70</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531131
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531923
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533137
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532467
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_86</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530943
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532821
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531321
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530943
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532469
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531829
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_79</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530279
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531207
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_85</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531775
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540089
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530445
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532123
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_69</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531923
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540363
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536691
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534649
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_76</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533961
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533223
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531021
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534267
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539825
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531239
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535473
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_84</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532581
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533569
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_77</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540423
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530595
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530787
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_68</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538205
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531387
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_67</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531511
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536853
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_74</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530395
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538299
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531113
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28566369
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530867
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28546517
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531239
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539839
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531293
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532301
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536145
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531833
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532693
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_89</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530163
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530799
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530933
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539553
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_66</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535223
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_90</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534227
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_71</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532081
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534713
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531337
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535035
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531821
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_88</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530595
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531083
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533487
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533887
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542437
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28547671
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_91</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540641
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531487
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530399
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530811
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_93</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533977
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531235
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532741
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532125
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531149
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_83</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530943
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539373
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531239
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534405
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_78</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542813
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530595
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530967
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530939
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534441
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542603
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28537427
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531277
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530163
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532209
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530145
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533389
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530399
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533995
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_82</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531775
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28541463
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530961
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_75</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531525
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_81</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535305
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_80</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531201
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538641
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536867
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_30_1617227_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535683
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532117
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530399
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530811
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533995
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539085
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531655
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530751
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532077
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530167
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531149
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531021
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530395
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531775
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540089
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28541463
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530445
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530525
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530331
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531239
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539839
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534405
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535473
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531489
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532121
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534649
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542813
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533281
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533487
-----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533887
------http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542437
-------http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28547671
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540423
----http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28537979
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531487
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532125
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28537427
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530341
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535035
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28566369
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531833
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532693
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531571
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538299
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536853
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532581
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531235
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531119
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536267
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533477
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534713
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533339
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536145
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533977
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542603
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535683
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532825
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530279
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531719
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532169
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531207
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531257
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532669
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530135
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534267
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531997
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531387
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540641
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538205
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533569
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535305
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532741
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531923
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28540363
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533137
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28535223
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530161
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28542189
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530163
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530799
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532209
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530865
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530653
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530455
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533223
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530645
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530961
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531771
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530623
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530249
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536867
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531525
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531511
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532081
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532123
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532113
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531131
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531277
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531113
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530711
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532637
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530335
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530225
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534227
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531829
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532467
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531321
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531821
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530933
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531799
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533961
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530145
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533389
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531933
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539563
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530269
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534005
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530377
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530943
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532469
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539373
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532821
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531337
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530939
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530595
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531083
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530967
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530787
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531293
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532737
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28532301
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530151
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533895
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539553
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539825
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28539301
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28536691
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531201
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28538641
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531043
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28533485
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28534441
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530867
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28546517
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28530219
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_30_1617227.24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_30_1617227.28531623
</commentlist>
</conversation>
