Feedback greatly appreciated...
Hello Michal,
This sounds like a great idea! Obviously, perchild is dead, so needs a
replacement. MetuxMPM doesn't handle SSL at all, which is a serious
limitation for anyone who wants to use it seriously (after all, who uses
a perchild model for security
On Mon, 18 Jul 2005, Michal Kosek wrote:
Implementation issues
Dispatcher
It would be best to make dispatcher single-threaded, I suppose that
creating separate thread for each connection would take much more
resources. OTOH it may cause some problems. One I am currently
some of the maintainers are still watching the
move.
Hideki Noma
Hi,
I'm going to make a new MPM (I called it Dispatching MPM, or D-MPM) that
would do what perchild is supposed to do. Here is a rough proposal of
the architecture.
My general idea is shown on the following diagram of example
On Mon, 18 Jul 2005, Michal Kosek wrote:
[ replying as I read - some points here which you address later ]
It would be great to see feedback from the authors of the original
perchild here - I'd guess you'll have insights into the difficulties
Michal is likely to face.
System consists of 3
On Tue, Jul 19, 2005 at 11:14:51AM +0100, Nick Kew wrote:
In presented example, client1 has specified Host: header and has been
redirected to worker1, while client2 hasn't specified it yet, so it is
still connected to the dispatcher. The diagram is created with
assumption that socket
On Tue, Jul 19, 2005 at 04:05:06PM +0900, Hideki Noma wrote:
Did you check Metux MPM?
It works by passing socket discriptor to worker process.
Yes, I looked at Metux MPM, but it also passes descriptors in the same
way as perchild, from process handling one vhost to another, and I don't
like it.
Hi,
I'm going to make a new MPM (I called it Dispatching MPM, or D-MPM) that
would do what perchild is supposed to do. Here is a rough proposal of
the architecture.
My general idea is shown on the following diagram of example state of
D-MPM
