Home

ASAP is about transparency and full control, though.

• Who has control (and can eavesdrop) on the connection?
• Who could be aware that a connection exists?

Spying on or changing of data is not a serious issue since we have end-to-end encryption. Have a look in our PKI-component.

There is simple rule: As longer the communication range as cheaper is spying. Tracking Internet communication requires access to routers. Convince providers to grant access and you are in. It is not really a matter of equipment and personal.

Short range ad-hoc networks like Bluetooth (less than 100m) but also Long-Range-Wan (few kilometres) are a different story. A pretty reasonable number of material is required to even realize that something happens, before an eavesdropping operation can start. It is realistic to set up a system even for smaller applications.

But, of course, most mobile application do not work short-range only. We need to use the Internet.

Technically, we could simply open a port on peers' device and allow other peers to connect. In reality, that would be an extrem security hazard.

So, we had no choice but to offer our ASAP Hub. A hub is a process. It opens a TCP port. Other processes can connect.

Now, we have a distributed system. A peer can connect a hub. There is a peer side API and a hub side API. Most developers will just need the peer side.

Peer and hub side exchange data via a little ASAP hub protocol.

It provides e.g. a list of connected devices. A hub can be asked to create a connection between to peers. In that case, a new thread is started on the hub that shovels bytes from one side to the other.