Introducing the data sending page


Getting Started

This page contains a list of all data items that the current endpoint is serving for the target endpoint through the current connection. The names for the said endpoints and connection are shown inside the dark bar under the main menu. The data transfer must be triggered on the target endpoint.

There are two phases in a data transfer in 1-NET:

  • The first one is triggered from the sending endpoint, namely the current endpoint. A progress panel will appear on both endpoints involved during the progression of this phase. The data is not transferred in this phase, only a set of very small hash values for the data are sent.
  • The second one is triggered on the receiving endpoint, namely the target endpoint. A progress panel will also appear on both endpoints involved during the progression of this phase. If the target endpoint is an APP or desktop program, then for each connection the user has the option of whether or not to receive data automatically for items transmitted over the connection. The setting can be done either on the corresponding connection inside connections page or inside the corresponding data sink page on the target endpoint. Browser receiving endpoints do not have such a level of automation, all data has to be received manually in there.

The file information is loaded into the APP or desktop program the first time one tries to send to file. However, such information is lost whenever the page is reloaded. When the current endpoint is an APP or desktop program, it can reload the said information automatically when requested at target endpoint before receiving the data there. For browser endpoints, such information is not loaded automatically whenever the page is reloaded, the user has to go back here to reload it manually before receiving the data on the target endpoint when the said information is lost.

When the file is not ready the reload button will appear in front of an item, giving the user the option of reloading the file on the current endpoint, albeit this is not likely to be needed in most of the cases.


Rendered in: 19 ms