Package java.net
The java.net package can be roughly divided in two sections:
A Low Level API, which deals with the following abstractions:
Addresses, which are networking identifiers, like IP addresses.
Sockets, which are basic bidirectional data communication mechanisms.
Interfaces, which describe network interfaces.
-
A High Level API, which deals with the following abstractions:
URIs, which represent Universal Resource Identifiers.
URLs, which represent Universal Resource Locators.
Connections, which represents connections to the resource pointed to by URLs.
Addresses
Addresses are used throughout the java.net APIs as either host identifiers, or socket endpoint identifiers.
The InetAddress class is the abstraction representing an
IP (Internet Protocol) address. It has two subclasses:
Inet4Addressfor IPv4 addresses.Inet6Addressfor IPv6 addresses.
But, in most cases, there is no need to deal directly with the subclasses, as the InetAddress abstraction should cover most of the needed functionality.
About IPv6
Not all systems have support for the IPv6 protocol, and while the Java
networking stack will attempt to detect it and use it transparently when
available, it is also possible to disable its use with a system property.
In the case where IPv6 is not available, or explicitly disabled,
Inet6Address are not valid arguments for most networking operations any
more. While methods like InetAddress.getByName(java.lang.String) are
guaranteed not to return an Inet6Address when looking up host names, it
is possible, by passing literals, to create such an object. In which
case, most methods, when called with an Inet6Address will throw an
Exception.
Sockets
Sockets are means to establish a communication link between machines over the network. The java.net package provides 4 kinds of Sockets:
Socketis a TCP client API, and will typically be used to connect to a remote host.ServerSocketis a TCP server API, and will typically accept connections from client sockets.DatagramSocketis a UDP endpoint API and is used to send and receive datagram packets.MulticastSocketis a subclass ofDatagramSocketused when dealing with multicast groups.
Sending and receiving with TCP sockets is done through InputStreams and
OutputStreams which can be obtained via the
Socket.getInputStream() and
Socket.getOutputStream() methods.
Interfaces
The NetworkInterface class provides APIs to browse and
query all the networking interfaces (e.g. ethernet connection or PPP
endpoint) of the local machine. It is through that class that you can
check if any of the local interfaces is configured to support IPv6.
Note, all conforming implementations must support at least one
NetworkInterface object, which must either be connected to a
network, or be a "loopback" interface that can only communicate with
entities on the same machine.
High level API
A number of classes in the java.net package do provide for a much higher level of abstraction and allow for easy access to resources on the network. The classes are:
URIis the class representing a Universal Resource Identifier, as specified in RFC 2396. As the name indicates, this is just an Identifier and doesn't provide directly the means to access the resource.URLis the class representing a Universal Resource Locator, which is both an older concept for URIs and a means to access the resources.URLConnectionis created from a URL and is the communication link used to access the resource pointed by the URL. This abstract class will delegate most of the work to the underlying protocol handlers like http or https.HttpURLConnectionis a subclass of URLConnection and provides some additional functionalities specific to the HTTP protocol. This API has been superseded by the newer HTTP Client API.
The recommended usage is to use URI to identify
resources, then convert it into a URL when it is time to
access the resource. From that URL, you can either get the
URLConnection for fine control, or get directly the
InputStream.
Here is an example:
URI uri = new URI("http://www.example.com/");
URL url = uri.toURL();
InputStream in = url.openStream();
Protocol Handlers
As mentioned, URL and URLConnection rely on protocol handlers which must be present, otherwise an Exception is thrown. This is the major difference with URIs which only identify resources, and therefore don't need to have access to the protocol handler. So, while it is possible to create an URI with any kind of protocol scheme (e.g.myproto://myhost.mydomain/resource/),
a similar URL will try to instantiate the handler for the specified protocol;
if it doesn't exist an exception will be thrown.
By default the protocol handlers are loaded dynamically from the default
location. It is, however, possible to deploy additional protocols handlers
as services. Service providers of type
URLStreamHandlerProvider are located at
runtime, as specified in the URL constructor.
Additional Specification
- Since:
- 1.0
-
ClassDescriptionThe class Authenticator represents an object that knows how to obtain authentication for a network connection.The type of the entity requesting authentication.Signals that an error occurred while attempting to bind a socket to a local address and port.Represents channels for storing resources in the ResponseCache.Represent channels for retrieving resources from the ResponseCache.Signals that an error occurred while attempting to connect a socket to a remote address and port.The abstract class
ContentHandleris the superclass of all classes that read anObjectfrom aURLConnection.This interface defines a factory for content handlers.A CookieHandler object provides a callback mechanism to hook up a HTTP state management policy implementation into the HTTP protocol handler.CookieManager provides a concrete implementation ofCookieHandler, which separates the storage of cookies from the policy surrounding accepting and rejecting cookies.CookiePolicy implementations decide which cookies should be accepted and which should be rejected.A CookieStore object represents a storage for cookie.This class represents a datagram packet.This class represents a socket for sending and receiving datagram packets.Abstract datagram and multicast socket implementation base class.This interface defines a factory for datagram socket implementations.A simple interface which provides a mechanism to map between a file name and a MIME type string.An HttpCookie object represents an HTTP cookie, which carries state information between server and user agent.Thrown to indicate that a HTTP request needs to be retried but cannot be retried automatically, due to streaming mode being enabled.A URLConnection with support for HTTP-specific features.Provides methods to convert internationalized domain names (IDNs) between a normal Unicode representation and an ASCII Compatible Encoding (ACE) representation.This class represents an Internet Protocol version 4 (IPv4) address.This class represents an Internet Protocol version 6 (IPv6) address.This class represents an Internet Protocol (IP) address.This class implements an IP Socket Address (IP address + port number) It can also be a pair (hostname + port number), in which case an attempt will be made to resolve the hostname.This class represents a Network Interface address.A URL Connection to a Java ARchive (JAR) file or an entry in a JAR file.Thrown to indicate that a malformed URL has occurred.AMulticastSocketis a datagram socket that is convenient for sending and receiving IP multicast datagrams.This class is for various network permissions.This class represents a Network Interface made up of a name, and a list of IP addresses assigned to this interface.Signals that an error occurred while attempting to connect a socket to a remote address and port.The class PasswordAuthentication is a data holder that is used by Authenticator.Signals that an ICMP Port Unreachable message has been received on a connected datagram.Thrown to indicate that there is an error in the underlying protocol, such as a TCP error.Represents a family of communication protocols.This class represents a proxy setting, typically a type (http, socks) and a socket address.Represents the proxy type.Selects the proxy server to use, if any, when connecting to the network resource referenced by a URL.Represents implementations of URLConnection caches.Represents a cache response originally retrieved through secure means, such as TLS.This class implements server sockets.This class implements client sockets (also called just "sockets").This class represents a Socket Address with no protocol attachment.Thrown to indicate that there is an error creating or accessing a Socket.The abstract classSocketImplis a common superclass of all classes that actually implement sockets.This interface defines a factory for socket implementations.SocketOption<T>A socket option associated with a socket.Interface of methods to get/set socket options.This class represents access to a network via sockets.Signals that a timeout has occurred on a socket read or accept.Defines the standard families of communication protocols.Defines the standard socket options.A Unix domain socket address.Thrown to indicate that the IP address of a host could not be determined.Thrown to indicate that an unknown service exception has occurred.Represents a Uniform Resource Identifier (URI) reference.Checked exception thrown to indicate that a string could not be parsed as a URI reference.ClassURLrepresents a Uniform Resource Locator, a pointer to a "resource" on the World Wide Web.This class loader is used to load classes and resources from a search path of URLs referring to both JAR files and directories.The abstract classURLConnectionis the superclass of all classes that represent a communications link between the application and a URL.Utility class for HTML form decoding.Utility class for HTML form encoding.Represents permission to access a resource or set of resources defined by a given url, and for a given set of user-settable request methods and request headers.The abstract classURLStreamHandleris the common superclass for all stream protocol handlers.This interface defines a factory forURLstream protocol handlers.