Re: gsoc project - Tomcat proxy [query]

2009-04-18 Thread Sharmistha jat
 Please find my wiki page about existing servlet proxy at :
http://wiki.apache.org/tomcat/ServletProxy

 I will continue to add information to this page, please suggest any
changes if required


On Thu, Apr 16, 2009 at 8:44 AM, Sharmistha jat
sharmistha.ja...@gmail.com wrote:
 Thanks for suggestion. [:)]

 On Thu, Apr 16, 2009 at 5:50 AM, Costin Manolache cos...@gmail.com wrote:
 One suggestion: I think it would be nice to consider scalability - if you
 have one tomcat frontend forwarding to 100 backends and acting as a load
 balancer - you probably can't afford one connection per thread. Many of the
 http forwarders I know use a blocking http client library - I think this
 would be the wrong approach for tomcat.

 To do non-blocking you will need to work at coyote level, and probably make
 few enhancements to register your client connection with the same framework
 - i.e. use the same Selectors or APR poll.
 You would also need to implement a non-blocking http client - you can use
 the nio/apr as starting points as well, but the code is a bit messy ( IMHO
 ). Or you could just start from scratch - use an existing non-blocking http
 client.

 I have a small experimental async http client in sandbox, if you plan to go
 non-blocking it may be worth checking it out (I'll update it to what I have
 - it's kind-of-working ). But probably using the NIO/APR connectors would be
 a better starting point.

 Costin

 On Wed, Apr 15, 2009 at 1:18 PM, jean-frederic clere 
 jfcl...@gmail.comwrote:

 Sharmistha jat wrote:

  So, now i would try to install a tomcat cluster and make a simple
 servlet proxy [reverse] for it, then add in load-balancing logic to it


 Yep thst is the idea.

 +++ CUT +++


  I have studied a number of servlet proxies like  j2ep, noodle  Http
 Proxy
 Servlet in past days.

 Could you write a wiki on that? (Somewhere in
 http://wiki.apache.org/tomcat/).


         i guess u mean writing wiki about proxy servlet
         will give my best shot to it, but would borrow 3-4 days for the
 task.


 You looked to the j2ep, noodle etc, don't you? It would be nice to describe
 a little how they work or that least their main features and the url to
 there code if applicable. Just like a note on other existing implementation.

     Ok, will write a wiki on the existing servlet proxies, their
 approach and working [thanks]

 Cheers

 Jean-Frederic


  Cheers

 Jean-Frederic

  And was puzzled about my intent of making proxy and its designing
 thereof.

 So, please guide me a little bit about this.

 Thanks
 Sharmistha


 -
 To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: dev-h...@tomcat.apache.org




 -
 To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: dev-h...@tomcat.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org



gsoc project - Tomcat proxy [query]

2009-04-15 Thread Sharmistha jat
Dear All,

I have applied for tomcat proxy project, but i needed a little more
information than given in the project idea, to start with the design of
proxy.

So i would like to know more about the following:

1) Type of proxy [reverse,content filter,caching etc].

2) Use [intent]

I have studied a number of servlet proxies like  j2ep, noodle  Http Proxy
Servlet in past days.

And was puzzled about my intent of making proxy and its designing thereof.

So, please guide me a little bit about this.

Thanks
Sharmistha


  v javascript://nop/


Re: gsoc project - Tomcat proxy [query]

2009-04-15 Thread Sharmistha jat
Thanks for suggestion. [:)]

On Thu, Apr 16, 2009 at 5:50 AM, Costin Manolache cos...@gmail.com wrote:
 One suggestion: I think it would be nice to consider scalability - if you
 have one tomcat frontend forwarding to 100 backends and acting as a load
 balancer - you probably can't afford one connection per thread. Many of the
 http forwarders I know use a blocking http client library - I think this
 would be the wrong approach for tomcat.

 To do non-blocking you will need to work at coyote level, and probably make
 few enhancements to register your client connection with the same framework
 - i.e. use the same Selectors or APR poll.
 You would also need to implement a non-blocking http client - you can use
 the nio/apr as starting points as well, but the code is a bit messy ( IMHO
 ). Or you could just start from scratch - use an existing non-blocking http
 client.

 I have a small experimental async http client in sandbox, if you plan to go
 non-blocking it may be worth checking it out (I'll update it to what I have
 - it's kind-of-working ). But probably using the NIO/APR connectors would be
 a better starting point.

 Costin

 On Wed, Apr 15, 2009 at 1:18 PM, jean-frederic clere jfcl...@gmail.comwrote:

 Sharmistha jat wrote:

  So, now i would try to install a tomcat cluster and make a simple
 servlet proxy [reverse] for it, then add in load-balancing logic to it


 Yep thst is the idea.

 +++ CUT +++


  I have studied a number of servlet proxies like  j2ep, noodle  Http
 Proxy
 Servlet in past days.

 Could you write a wiki on that? (Somewhere in
 http://wiki.apache.org/tomcat/).


         i guess u mean writing wiki about proxy servlet
         will give my best shot to it, but would borrow 3-4 days for the
 task.


 You looked to the j2ep, noodle etc, don't you? It would be nice to describe
 a little how they work or that least their main features and the url to
 there code if applicable. Just like a note on other existing implementation.

 Ok, will write a wiki on the existing servlet proxies, their
approach and working [thanks]

 Cheers

 Jean-Frederic


  Cheers

 Jean-Frederic

  And was puzzled about my intent of making proxy and its designing
 thereof.

 So, please guide me a little bit about this.

 Thanks
 Sharmistha


 -
 To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: dev-h...@tomcat.apache.org




 -
 To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
 For additional commands, e-mail: dev-h...@tomcat.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org