tutorial_en_s2s
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| tutorial_en_s2s [2014/07/06 06:57] – created xirvdev | tutorial_en_s2s [2014/10/14 08:28] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 44: | Line 44: | ||
| Notes: | Notes: | ||
| + | |||
| - The files you receive take space. It's obvious, but keep it in mind. You need to have enough storage to receive the files, and leaving the S2S endpoint open longer than needed may fill up your account if the sender continue to send files. | - The files you receive take space. It's obvious, but keep it in mind. You need to have enough storage to receive the files, and leaving the S2S endpoint open longer than needed may fill up your account if the sender continue to send files. | ||
| + | |||
| - The sender cannot tell how much available storage you have. | - The sender cannot tell how much available storage you have. | ||
| + | |||
| - Even if the system is designed for privacy you should share endpoints with specific users, or leave them open for a very short time in which you are monitoring usage (for example, saying in the shoutbox "I can't find the last Ubuntu ISO, can someone upload it to this S2S endpoint: XXXXXXXXXXX?" | - Even if the system is designed for privacy you should share endpoints with specific users, or leave them open for a very short time in which you are monitoring usage (for example, saying in the shoutbox "I can't find the last Ubuntu ISO, can someone upload it to this S2S endpoint: XXXXXXXXXXX?" | ||
| + | |||
| - The S2S endpoints are receive only. You cannot access the files in someone else's endpoint even if you have the ID. You can send files to it but you cannot see the endpoint contents or download them. | - The S2S endpoints are receive only. You cannot access the files in someone else's endpoint even if you have the ID. You can send files to it but you cannot see the endpoint contents or download them. | ||
| + | |||
| - Behind the scenes the transfer happens via SFTP using one thread. It competes for bandwidth with the rest of the things going on in both servers. | - Behind the scenes the transfer happens via SFTP using one thread. It competes for bandwidth with the rest of the things going on in both servers. | ||
| + | |||
| - The system is still in beta. Seems to works fine but be aware of it. Please send reports if you find any bug. | - The system is still in beta. Seems to works fine but be aware of it. Please send reports if you find any bug. | ||
tutorial_en_s2s.1404629865.txt.gz · Last modified: 2014/10/14 08:28 (external edit)