quote:
Originally posted by kabso 5
But when we send files it shows the KB left and transfer and if it goes to a server we should notice the lag, I dont understand how do the files go to a server by " uploading " then the other person is "downloading", It looks more like an e-mail and It'll be much slower if its like that, because when we are sending a file into the messenger convo it must upload all the file at once and after finishing the upload the download will start, if it was by uploading and downloading method.
That 'method' doesn't have anything todo with how the files are transfered (directly or via MS' servers). In either case you could make it that you first need to upload completely before downloading anything or not, and vice versa. That's just how the sending/receiving protocol works, it doesn't say a thing about via what way it is transfered. Those two things don't have anything todo with eachother and thus are not an indication of how files (or other things) are transfered.
To put it in another way: what you just described is how packets (the small parts of the complete file) are handled, nothing more. It does not describe the physical pathway the packets will take. eg: First you always need to send a portion of the file before the contact can download that portion, of course. But it does not say a thing about what path that portion has taken to get to the contact. It might have been directly: P2P, or it might have gone thru 10 different servers, it doesn't matter. In either case you first need to upload something before the other party can download it. And in the case of Messenger, the contact can start downloading as soon as you start uploading.
Files are also not temporary stored in the case of Messenger. This means that it is your contact who initiates the uploading and thus concequently the downloading. If the contact stops downloading, you will stop uploading (and vice versa). But this has again nothing todo with what physical path the files will take.
The same for speed; speed does not have anything todo with how files are transfered. You can have a very slow P2P connection, but a fast indirect pathway (it wouldn't happen a lot in practice, but it is possible).
Proof of all this can be seen by the fact that nomatter how the files are transfered, the UI handling is always the same: you send a request to initiate a file transfer, your contact excepts and starts the actual transfering. It is always the same scheme eventhough sometimes the files will be transfered P2P and sometimes via MS' servers.
/ 
