Text 6293, 100 rader
Skriven 2005-03-27 23:13:00 av CHARLES ANGELICH (1:123/140)
     Kommentar till en text av GERALD MILLER
Ärende: torrent
===============

123c54a1db4c
win95



Hello Gerald - 

GM> about: torrent 

GM> [trim] 

CA>> There is no 'server' when using a torrent it's not unlike
CA>> P2P shares. There is one machine that is the trakker that
CA>> initiates the process (someone has to have the entire file
CA>> to start the process) but after that it's all just sharing
CA>> of pieces of the file. The author of BitTorrent claims it
CA>> can manage 1000 times more downloads than server software
CA>> could manage within the same timeframe. 

GM> Ingenuously clever technique! 

Another ingenuously clever idea is to name a file as a pr0n
file then add it to the torrents. It remains there indefinitely
being 'shared' by 1000s of 'collectors'. A sort of infinite
storage/archvie. :-) 

GM>>> What I don't understand is how I change the "torrent"
GM>>> file to an "ISO" file that Nero can burn. 

CA>> There is no "torrent" that is just the protocol being used
CA>> for the transfers rather than HTTP or FTP etc. The file is
CA>> whatever it is. If you are transferring an MOV, MP3, or
CA>> ISO file that is what the file is. All torrents do not
CA>> involve ISO files. Many are MP3s while some are AVIs. 

GM> The file type is encoded in a header? 

Possibly. I'm not intimately familiar with each phase involved
in transferring a torrent file. 

CA>> An "ISO" file is comparable to a photograph of the file
CA>> layout on whatever storage media it was on. ISOs can be
CA>> image copies of a floppy disk, zipdisk, CD rom, DVD, or an
CA>> entire partition of a hard drive. The ISO can contain many
CA>> files but the ISO itself is one continuous file that must
CA>> be returned to media as an ISO that overlays the entire
CA>> surface of that media (or single partition on a hard
CA>> drive). Another way of expressing this is that the ISO is
CA>> a _binary_copy_ of what is stored on the media copied
CA>> without regard to media formats of the particular OS that
CA>> created the information originally. 

GM> That is probably the best explanation of "ISO" that I've
GM> encountered. Very concise and clear (to me)! 

Thank you. 

GM> [trim] 

GM>>> Is the file automatically renamed after the download has
GM>>> completed? 

CA>> Using _my_ torrent transfer software the file temporarilly
CA>> has some gibberish appended to the start that is
CA>> removed/replaced by the actual filename upon completion. 

GM> I'm still unclear about the "torrent transfer software"...
GM> If it is part of the TCP/IP suite of protocols, then _most_
GM> Windows systems _should_ be able to deal with the
GM> "gibberish" upon completion. 

TCP/IP is a packet transfer with 'addressing' that moves data
in 'chunks'. Other protocols feed the data to TCP/IP which cuts
up the 'chunks' and then reassembles it at the receiving end.
Torrent files do the same thing from within TCP/IP which is a
packet transfer within a packet transfer. Sort of. :-) 

GM>>> Or is there something that I'm missing about the whole
GM>>> procedure? 

CA>> Only that the "torrent" refers to the URL of the trakker
CA>> _and_ the filename of the file being transferred. 

GM> When I've completed the fix for the W2K system, I'll send
GM> e-mail to Alan Z. for more details or for the URL (again)
GM> of the Win Knoppix... 

OK 

>
>        ,                          ,
>      o/      Charles.Angelich      \o       ,
>     <|                              |>  __o/
>     / >          USA, MI           < \   __\__
 

--- * ATP/16bit 2.31 * 
... DOS the Ghost in the Machine! http://www.devedia.com/dosghost/
 * Origin: Try Our Web Based QWK: DOCSPLACE.ORG (1:123/140)