Peer to Peer Connections
This is a key advantage of Beyond FTP. In the typical FTP client/server implementation, all actions must be initiated by the client. The server is simply a passive actor. A Beyond FTP server, however, can initiate actions involving other Beyond FTP servers and/or Beyond FTP clients. This allows central control of the entire transfer process, if necessary.
There are several things to keep in mind when implementing multiple Beyond FTP sites.
1. Beyond FTP servers and clients are named. The Address Book entry used to call a remote Beyond FTP server must have the same name as that server. This is most easily accomplished by allowing Beyond FTP to retrieve the name by pressing Get Server Name .
2. Beyond FTP connections do not use the standard FTP port. The default port value is 35091, and is configured in the Console. Firewalls must allow calls on this port. If this is not possible, Beyond FTP supports SOCKS4 and SOCKS5 proxy protocols.
3. Beyond FTP connections are completely encrypted. A proprietary scheme is applied to all traffic. This can be augmented by more advanced, private key encryption. For this reason, there is no protocol that is visible to a proxy or a firewall. They must allow transparent, bi-directional traffic.
4. Since Beyond FTP connections can be initiated by either a client or a server, both sides employ Beyond FTP security accounts to control user access. This gives flexibility in the manner rights are assigned and allows you to grant access to all disk resources supported by a particular machine. There is no “root” concept like you find in FTP servers.