Netlib API

Introduction

The Netlib API covers the two part needed for (anonymous) communication:

• bidirectional byte streams using different network protocols: see [Netlib NetLayer] for details
• name resolution using different network protocols: see [Netlib NetAddressNameService] for details

While the motivation of the first part is quite clear, the motivation of the second is usually not obvious: One important point in anonymous communication is to control DNS request. It is important that DNS requests related to the anonymous communication are NOT sent to the local DNS server - otherwise these unsecured DNS requests could be used to analyse the anonymous communication.

Basic Ideas of the Netlib API

• the API provides a common interfaces to the specific protocol and service implementations
• definition of the API uses Java interfaces instead of Java classes to avoid unneeded dependencies
  • we use interfaces NetLayer and NetSocket/NetServerSocket instead of classes java.net.Socket/java.net.ServerSocket
  • we use interfaces NetAddressNameService and NetAddress instead of class java.net.InetAddress
• the usage of the Netlib API is very similar to the usage of the standard java.net API

---

Top : [Netlib], Next : [Netlib NetLayer]