On Sun, 2007-06-10 at 20:55 -0700, Sachin Mehrotra wrote: > Hi, > > We are actually trying to build our own full fledged HTTP Server using HTTP > Components APIs. > Currently HTTO Core alone is not sufficient to fulfill our requirement that's > why we want to know to know whether in coming release of HTTP components will > there be APIs to support all the features of a HTTP Server. And also we want > to put our own SSL implementation so will there be anything to support that. > > Thanks, > Sachin >
Sachin, We are precluded from building a light-weight HTTP server implementation by the project charter due to political reasons. This is the reason why we are mainly focusing on developing core and client-side HTTP components for the time being. Development of a custom SSL engine is clearly out of the project scope. Besides, none of us is a cryptography expert to begin with. Why would you want to develop a full-blown SSL engine in the first place? There is another thing I would like to mention. If your development efforts are backed and funded by a commercial company, another possibility would be to build missing server-side components in house and to contribute them back to the project. Cheers Oleg > > -----Original Message----- > From: Oleg Kalnichevski [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 09, 2007 3:21 PM > To: HttpComponents Project > Subject: RE: Regarding HTTPComponents functioning. > > On Fri, 2007-06-08 at 21:11 -0700, Sachin Mehrotra wrote: > > Hi, > > > > So can we use these HTTP Client APIs in our HTTP Server Development for > > needed support which i mentioned. > > > > Thanks, > > Sachin > > > > Sachin, > > You mentioned you needed APIs for cookie handling, but you did not > specify whether you needed components for client-side cookie handling, > server-side cookie handling or both. > > So, what is it you are trying to achieve?. Are you developing a proxy of > a kind? If so, you may need some client-side HTTP components (for cookie > handling in outgoing requests, connection pooling and so on). If you are > developing what is effectively a custom servlet engine, then client-side > cookie API is of little use. > > Hope this helps, > > Oleg > > > ________________________________ > > > > From: Ortwin Glück [mailto:[EMAIL PROTECTED] > > Sent: Fri 6/8/2007 5:38 AM > > To: HttpComponents Project > > Subject: Re: Regarding HTTPComponents functioning. > > > > > > > > Sachin, > > > > Connection management is currently implemented only in the HttpClient > > (4.0) project, but not in HttpCore. There you can find socket factories > > to plugin your SSL implementation: > > http://svn.apache.org/viewvc/jakarta/httpcomponents/httpclient/trunk/module-client/src/main/java/org/apache/http/conn/SecureSocketFactory.java?view=markup > > > > Same for cookies. API is here: > > http://svn.apache.org/viewvc/jakarta/httpcomponents/httpclient/trunk/module-client/src/main/java/org/apache/http/cookie/ > > > > I agree that this is currently a bit "hidden" and not clear from the > > website. > > > > Cheers > > > > Ortwin > > > > Sachin Mehrotra wrote: > > > Hi, > > > > > > > > > > > > We are planning to use HTTP Components for our HTTP Stuff. We have some > > > questions...... > > > > > > > > > > > > a) We haven't found APIs for placing our Custom SSL > > > Implementation. > > > > > > b) We haven't found any API's for Cookies handling. > > > > > > > > > > > > Is there any planning for support of the above? > > > > > > > > > > > > Thanks, > > > > > > Sachin > > > > > > > > > > -- > > [web] http://www.odi.ch/ > > [blog] http://www.odi.ch/weblog/ > > [pgp] key 0x81CF3416 > > finger print F2B1 B21F F056 D53E 5D79 A5AF 02BE 70F5 81CF 3416 > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
