taoyang987 / http4j Goto Github PK

Need to support chunked message.

currently we just close it if HTTP version is 1.0.
below scenario should be considered:
1. connection:close
2. without keep alive header
3...

User should be able to set "followRedirect" in Client.
It will be very useful while user do not care HTTP 3XX response.

Consider of using Guava in http4j:
Guava's google-collection & google-io

我使用POST，结果POST的参数没有传过去，请问POST如何使用？

Whether to cache DNS should be an option.
To be a config method.

URL Encoding Feature

DNS Cache Feature

Cookie Manager/Cache Feature

Too many exceptions declared in methods.
Need to define own exceptions.

Client should be able to record both response and redirected response metrics.
Have to consider a linked data structure in Metrics class.

Performance is bad.
Consider increase io buffer and other aproach.

Methods such as HEAD, PUT, etc. should be supported so that it could be used 
for restful sites.

People might be confused while they see:
in.read(bytes) and byteArrayOutputStream.write(bytes)

they might want to see:
int n = in.read(bytes) and byteArrayOutputStream.write(bytes, 0, n)

Current implementation:
Currently we use InputStreamWrapper to wrap the DataInputStream and encapsulate 
the readFully method in the backend.
As a result, each in.read(bytes) will read fully bytes.length data.
This might not be good for experienced developer to read, so we need reactor.

Client should be able to set max redirect times limitation to avoid too much 
redirection.

Multipart form support feature

Enable/Disable cookie cache.
Better to make it as config method in executor or client.
@see Guava's Collection configuration.

Some articles say that Socket Receive Buffer size should be multiple 1460 to 
get better performance.
Currently we use the default buffer size(8192).

See 
https://groups.google.com/group/http-archive-specification/web/har-1-2-spec?pli=
1

entry.time == entry.timings.blocked + entry.timings.dns +
    entry.timings.connect + entry.timings.send + entry.timings.wait +
    entry.timings.receive; 

Currently JDK CookieManager has a lot of bugs,and they will be fixed in Java7. 
So we have 3 options:
1. Implements Cookie Manager ourselves.
2. Wait for bug fix and change our dependency of java to 7.
3. Drop this feature.

http://search.oracle.com/search/search?group=Sun+Defects&site=bugs.sun.com&q=coo
kiemanager

HTTPS Feature

Connection management strategy(manage config?) should be support:
1. Use pool or not
2. max connection limitation
...
etc.