Dear all,
           
Pound is act as  a request redirector: requests may be distributed among
servers according to the requested URL. So i want to know whether this means
that Pound is a "content-aware" Load balancer, like Zeus Load Balancer ? And is
Pound developed in the Application layer?

Due to  the load balancing issues involve recognizing and understanding the
nature of individual web requests and responses. A Load Balancer should read
and understand requests, and then direct appropriately. So does Pound  inspect
every incoming HTTP request and makes further request forwarding decisions by
using some intelligent algorithms. If so,  Anyone can introduce that in some
detail ? 

Second, the dynamic generated content is being more and more, in this case, it
is impossible to inspect every incoming HTTP request and then direct
appropriately, so any solution to that situation?

Last, could anyone kindly give some suggestion on the choice between
Content-Aware and Non-Content-Aware  redirecting?

Thanks!
Anpool

In the spirit of getting you a quick answer: 

Visit http://www.apsis.ch/pound/ for a
very complete description of the
program.

To answer some of your questions... AFAIK, Pound is not "content-aware" by
design. It is designed to send requests to multiple identical back-end
webservers transparent to the client requesting information. Its very good at
what it does. However, you can use regular expressions to examine the URL, and
HTTP headers to intelligently determine where the request should go. You supply
the intelligence, and assume the liability for correctly being able to predict
based on URL and headers where your request needs to go. Again, see
http://www.apsis.ch/pound/ for some
detailed examples.

If anyone wants to elaborate on anything I've said, or correct me in any way,
please jump right in! :)

CG

--- anpool <ieanpool(at)ust.hk> wrote:[...]




	
		[...]