commit | 9be4e37109bd15724e5fc1cd753b61d90055084c | [log] [tgz] |
---|---|---|
author | Paul Hawke <[email protected]> | Tue May 21 23:03:30 2013 -0500 |
committer | Paul Hawke <[email protected]> | Tue May 21 23:03:30 2013 -0500 |
tree | 11d1ce93d9793119a8d26d4505ccccadfd8eb710 | |
parent | 84dcf74395d1817c4a2a7861bd5d3787daa6700a [diff] |
2.0.0 Release
NanoHttpd is a light-weight HTTP server designed for embedding in other applications.
NanoHttpd has been released under a Modified BSD licence.
index.html
and index.htm
./
.The project is managed with a “fork and pull-request” pattern. If you want to contribute, fork this repo and submit a pull-request of your changes when you're ready. Anyone can create Issues, and pull requests should be tied back to an issue describing the purpose of the submitted code.
The original (Java 1.1 project) and the Java 6 project merged in early 2013 to pool resources around “NanoHttpd” as a whole, regardless of flavor. Development of the Java 1.1 version continues as a permanent branch (“nanohttpd-for-java1.1”) in the main http://github.com/NanoHttpd/nanohttpd repository.
Firstly take a look at the “samples” sub-module. The sample code illustrates using NanoHttpd in various ways.
Secondly, you can run the standalone NanoHttpd Webserver.
Or, create your own class that extends NanoHTTPD
and overrides the serve()
method. For example:
public class DebugServer extends NanoHTTPD { /** * Constructs an HTTP server on given port. */ public DebugServer() { super(8080); } @Override public Response serve(String uri, Method method, Map<String, String> header, Map<String, String> parms, Map<String, String> files) { StringBuilder sb = new StringBuilder(); sb.append("<html>"); sb.append("<head><title>Debug Server</title></head>"); sb.append("<body>"); sb.append("<h1>Response</h1>"); sb.append("<p><blockquote><b>URI -</b> ").append(uri).append("<br />"); sb.append("<b>Method -</b> ").append(method).append("</blockquote></p>"); sb.append("<h3>Headers</h3><p><blockquote>").append(header).append("</blockquote></p>"); sb.append("<h3>Parms</h3><p><blockquote>").append(parms).append("</blockquote></p>"); sb.append("<h3>Files</h3><p><blockquote>").append(files).append("</blockquote></p>"); sb.append("</body>"); sb.append("</html>"); return new Response(sb.toString()); } public static void main(String[] args) { ServerRunner.run(DebugServer.class); } }
The Java 6 version of nanohttpd was born when we realized that embedding Jetty inside our Android application was going to inflate the size without bringing along features that we were going to need. The search for a smaller more streamlined HTTP server lead us to nanohttpd as the project had started with exactly the same goals, but we wanted to clear up the old code - move from Java 1.1, run static code analysis tools and cleanup the findings and pull out sample/test code from the source.
In the words of the original founder of the project
I couldn't find a small enough, embeddable and easily modifiable HTTP server that I could just copy and paste into my other Java projects. Every one of them consisted of dozens of .java files and/or jars, usually with - from my point of view - “overkill features” like servlet support, web administration, configuration files, logging etc.
Since that time we fixed a number of bugs, moved the build to maven and pulled out the samples from the runtime JAR to further slim it down.
The two projects pooled resources in early 2013, merging code-bases, to better support the user base and reduce confusion over why two NanoHttpd projects existed.
Thank you to everyone who has reported bugs and suggested fixes.