Hi Oleg, I am not quite sure about what HTTP parameter means. I think it means the HTTP headers. So I implemented some methods to set and get headers "fluently". You may find the example [1] and details [2] in Wiki. I used the jQuery (maybe also other frameworks and APIs do) style to design this part. if a method invoked with parameters, then it is a "setter", otherwise it is a "getter". Since there are lots of headers, and FluentRequest/Response also implements the interface HttpUriRequest/HttpResponse which provides the method setHeader(name,value) and addHeader(name,value), I think it is not necessary to cover all headers. What do you think about it?
[1] at the bottom of http://code.google.com/p/fluent-hc/wiki/RequestExecution [2] http://code.google.com/p/fluent-hc/wiki/HttpParameterConfigure Best, Lilu On Thu, Jun 2, 2011 at 9:39 AM, Oleg Kalnichevski <ol...@apache.org> wrote: > On Wed, 2011-06-01 at 18:40 +0300, Xu, Lilu wrote: > > Hi, > > > > I almost finished the request execution module and most classes have been > > re-designed. Please have a look at the wiki pages [1] of this project and > > drop me some comments. > > The wiki pages contain some simple examples to illustrate how to use the > > facade API of httpclient. > > > > [1] http://code.google.com/p/fluent-hc/w/list > > Hi Lilu > > I think it is a good start. I like it. > > There is still some ground to cover, though: HTTP parameter > configuration, authentication, etc. > > Oleg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org > For additional commands, e-mail: dev-h...@hc.apache.org > > -- Best regards, Lilu
