| Attn: SNS, RE: Unison |
|
| () |
2016/05/17 18:21 |
Path: news.nzbot.com!news.astraweb.com!border2.newsrouter.astraweb.com!newspeer1.nac.net!border2.nntp.dca1.giganews.com!Xl.tags.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!local2.nntp.dca.giganews.com!news.giganews.com.POSTED!not-for-mail
NNTP-Posting-Date: Tue, 17 May 2016 19:21:03 -0500
From: Griff
Newsgroups: alt.binaries.multimedia.cooking
Date: Tue, 17 May 2016 16:21:03 -0800
Message-ID: <2016051716210316807-@news.giganews.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Attn: SNS, RE: Unison
User-Agent: Unison/1.8.1
Lines: 56
X-Usenet-Provider: http://www.giganews.com
X-Trace: sv3-cookRn79as4jfKvPoG+VYM31QXYPBlY2RvLcqKMhgByLE56nEvPkUNLkhFGMQFr6wMH1fohiL14BeGM!ty5ELbRPUHnqauiXw2c7hRtmBPnuH0ADdk8QK6/0BICF70Nt78bl14kxP72pHryjUCA=
X-Complaints-To: abuse@giganews.com
X-DMCA-Notifications: http://www.giganews.com/info/dmca.html
X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers
X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly
X-Postfilter: 1.3.40
X-Original-Bytes: 3714
Xref: news.nzbot.com alt.binaries.multimedia.cooking:5425
SNS -
I DL'ed your latest post of A1617 without any apparent problems.
(Haven't watched it yet so final confirmation is pending.)
For reasons I don'e want to get into, I'm still running OSX 10.6.8 and
Unison 1.8.1. (I have a sizable data investment that I don't want to
risk by upgrading.)
I can provide a historical and technological perspective on what you're
experiencing. I began studying computer circuitry in 1967 and began
computer programming in 1970. I have continued doing that since, over
a wide range of areas, challenges, and responsibilities. In the early
80's, I started ongoing efforts to reliably transmit data over
distances, initially starting with 2400 baud modems sending data via
satellite telephone connections.
Initially, parity generation and data transmission were two separate
steps. Aggravating my efforts was technology for segmenting
(packetizing) large files had not yet been developed. At that point,
the larger the file, the greater the chance the entire transmission had
to be thrown into the bit bucket because of a momentary glitch on
transmission.
Segmenting the files (and the corresponding recombination) allowed for
only the corrupt segments needing to be retransmitted, rather than the
entire file. Breaking files up into small segments also allows the
Internet to operate more efficiently. (Internet efficiency is arguably
the main reason for developing packet transmission protocols.)
Up until fifteen or so years ago, users generate parity/error
correction files separately, before transmission. The parity/error
correction functionality was combined with the segmentation routines as
a reasonably cohesive combination of functionality.
Unison 1.x was unusual in it combine all three functions (packetizing,
parity generation, and transmission) into a single software entity.
This is a two-edged sword in terms of software engineering. It
provides more convenience for the user (always desirable) but
drastically increases the possibility an entire software entity could
be rendered obsolete by a technological change or advancement in one of
those areas.
It's worth noting that parity generation and error correction
technology is used in other areas besides data transmission, especially
in archival data storage. So, it is more likely to experience
fundamental changes than transmission technology.
So, you've effectively been forced to take a step backwards, towards
fundamentals, and divide your upload process into separate steps. I
understand your frustration with the additional effort required and
sincerely hope you will continue your greatly appreciated efforts in
spite of this frustration.
Griff
|
|
|