|Deletions are marked like this.||Additions are marked like this.|
|Line 56:||Line 56:|
| 1. [[HttpComponentsRoadmap|HttpComponents roadmap]] - (in)official development roadmap
Welcome to the HttpComponents Wiki
This wiki provides additional documentation for HttpClient and HttpComponents. Formal documentation is available from the HttpComponents website. Users are encouraged to contribute information to this wiki that may be useful to others.
To avoid spammers, only registered users can update the Wiki. Create a wiki login, and then send a brief request to the dev@ list asking to be added to the Contributors Group including your wiki username. No mailing list subscription required.
User information is meant for people using our components or Commons HttpClient 3.1, or for people considering to use them. For starters, we have a list of HttpClientPowered applications that use HttpClient. Then there is documentation and several FAQs in this list:
Guided Tour of HttpCore - Overview documentation for HttpComponents Core
Connection Management FAQ - What is TIME_WAIT etc
Lessons Learned from 100+ websites - Common website practices
We also keep a user documentation index on our website. It points to JavaDocs and example code not linked from this wiki.
If interested in I/O performance these benchmark results may be of interest: Blocking I/O vs NIO
Developer information is meant for people working on our project codebase, including the Java source code as well as the sources for generating our website.
The first set of links describes technical procedures:
WebSite - How to update and deploy the HttpComponents website
IssueTracking - How to get access to issue tracking on JIRA
HttpComponents release process - How to cut and publish a release of HttpComponents project
HttpComponents roadmap - (in)official development roadmap
Then we have some non-procedural information for reference:
JavaDocGuidelines - API JavaDoc guidelines for HttpComponents
ReferenceMaterials - Links to relevant standards
CodingConventions - Code formatting and coding standards that contributing developers should adhere to