org.webbitserver.WebServer Maven / Gradle / Ivy
Go to download
Show more of this group Show more artifacts with this name
Show all versions of webbit Show documentation
Show all versions of webbit Show documentation
A Java event based WebSocket and HTTP server
package org.webbitserver;
import java.io.IOException;
import java.net.URI;
import java.util.concurrent.Executor;
/**
* Configures an event based webserver.
*
* To create an instance, use {@link WebServers#createWebServer(int)}.
*
* As with many of the interfaces in webbitserver, setter style methods return a
* reference to this, to allow for simple initialization using method chaining.
*
* Hello World Example
*
* class HelloWorldHandler implements HttpHandler {
* void handleHttpRequest(HttpRequest request, HttpResponse response, HttpControl control) {
* response.header("Content-Type", "text/html")
* .content("Hello World")
* .end();
* }
* }
* WebServer webServer = WebServers.createWebServer(8080)
* .add(new HelloWorldHandler())
* .start();
* print("Point your browser to " + webServer.getUri());
*
*
* Serving Static Files
*
* WebServer webServer = WebServers.createWebServer(8080)
* .add(new StaticFileHandler("./wwwdata"))
* .start();
*
*
* @author Joe Walnes
* @see WebServers
* @see HttpHandler
* @see WebSocketConnection
* @see EventSourceConnection
*/
public interface WebServer {
/**
* Add an HttpHandler. When a request comes in the first HttpHandler will be invoked.
* The HttpHandler should either handle the request, or pass the request onto the
* next HttpHandler (using {@link HttpControl#nextHandler()}). This is repeated
* until a HttpHandler returns a response. If there are no remaining handlers, the
* webserver shall return 404 NOT FOUND to the browser.
*
* HttpHandlers are attempted in the order in which they are added to the WebServer.
*
* @see HttpHandler
*/
WebServer add(HttpHandler handler);
/**
* Add an HttpHandler that will only respond to a certain path (e.g "/some/page").
*
* This is shortcut for {@code add(newPathMatchHandler(path, handler))}.
*
* @see HttpHandler
* @see #add(HttpHandler)
* @see org.webbitserver.handler.PathMatchHandler
*/
WebServer add(String path, HttpHandler handler);
/**
* Add a WebSocketHandler for dealing with WebSockets.
*
* This is shortcut for {@code add(new PathMatchHandler(path, newHttpToWebSocketHandler(handler)))}.
*
* @see WebSocketHandler
* @see HttpHandler
* @see #add(HttpHandler)
* @see org.webbitserver.handler.HttpToWebSocketHandler
* @see org.webbitserver.handler.PathMatchHandler
*/
WebServer add(String path, WebSocketHandler handler);
/**
* Add a WebSocketHandler for dealing with WebSockets.
*
* This is shortcut for {@code add(new PathMatchHandler(path, newHttpToEventSourceHandler(handler)))}.
*
* @see HttpHandler
* @see #add(HttpHandler)
* @see org.webbitserver.handler.HttpToEventSourceHandler
* @see org.webbitserver.handler.PathMatchHandler
*/
WebServer add(String path, EventSourceHandler handler);
/**
* Start web server in background.
*/
WebServer start() throws IOException;
/**
* Stop web server background thread. This returns immediately, but the
* webserver may still be shutting down. To wait until it's fully stopped,
* use {@link #join()}.
*/
WebServer stop() throws IOException;
/**
* Call after {@link #stop()} to wait until webserver has stopped its background
* threads and closed all socket connections. This method blocks.
*/
WebServer join() throws InterruptedException;
/**
* What to do when an exception gets thrown in a handler.
*
* Defaults to using {@link org.webbitserver.handler.exceptions.PrintStackTraceExceptionHandler}.
* It is suggested that apps supply their own implementation (e.g. to log somewhere).
*/
WebServer uncaughtExceptionHandler(Thread.UncaughtExceptionHandler handler);
/**
* What to do when an exception occurs when attempting to read/write data
* from/to the underlying connection. e.g. If an HTTP request disconnects
* before it was expected.
*
* Defaults to using {@link org.webbitserver.handler.exceptions.SilentExceptionHandler}
* as this is a common thing to happen on a network, and most systems should not care.
*/
WebServer connectionExceptionHandler(Thread.UncaughtExceptionHandler handler);
/**
* Get base URI that webserver is serving on.
*/
URI getUri();
/**
* Get base port that webserver is serving on.
*/
int getPort();
/**
* Get main work executor that all handlers will execute on.
*/
Executor getExecutor();
/**
* Number of milliseconds before a stale HTTP keep-alive connection is closed by the server. A HTTP connection
* is considered stale if it remains open without sending more data within the timeout window.
*/
WebServer staleConnectionTimeout(long millis);
}