I have to do some HTTP-Method based filtering (in order to have a R/O and an
R/W subversion servers).
So, here is a quick and quite dirty patch that adds a new config param
"Method" inside a service.
Its state is : it works for me :-)
[...]

On Tue, 2007-04-24 at 07:43 +0200, Steve Schnepp wrote:[...]

Thanks Steve. We'll look at it in detail and integrate it into the next
experimental version if possible.[...]

On 4/25/07, Robert Segall <roseg(at)apsis.ch> wrote:[...]

Actually, I needed a proof of concept quite fast, that's why it's not
fullly tested. Actually, it doesn't work as intended for my purpose :
I don't share the subversion repository among the R/O and the R/W
servers (actually, in that case my patch works wonderfully).

I need a solution more application-aware and i don't think it's really
Pound's job.

But I would be glad to see how the code could be integrated in Pound,
and if I can I may help.
[...]

On Mon, 2007-04-30 at 11:14 +0200, Steve Schnepp wrote:[...]

I looked your patch over and I'm not entirely clear what it would give
you. Pound has request class filtering (see the xHTTP directive). If
what you want is to differentiate between read/write requests that is
not much help, as a simple GET or POST may include parameters. Care to
expand on this?[...]

On 4/30/07, Robert Segall <roseg(at)apsis.ch> wrote:[...]

Sure.

GET requests are read only and POST are R/W. The fact that they may
include parametres is not a problem (I think of it as SELECTs and
UPDATEs, which both can have parameters)

This way if you have a REST load-balanced application for example,
connected to load balanced master/slaves databases, you can
load/balance the read instead of having to load balance the database
part. [ I don't know if I explained it correctly ]
[...]