Re: Metuxmpm test failed
"Dmitry P. Schegolev" <[email protected]> Mon, 6 Oct 2003 11:40:01 +0400
| Newsgroups | gmane.comp.apache.metuxmpm |
|---|---|
| Message-ID | <[email protected]> |
- [email protected] --------------------------------------------------------------------- > Yes. But it does some tricks, i.e. passing the whole socket. > We do not process the whole request in the multiplexer. Who prevent us to use the same tricks in my model? <snip> > Yes, it is cleaner, but much slower. Your approach requires the whole > data to be passed over multiple process boundaries - this produces load. From this point of view: we need to decrypt data. So it's not the same data, as got from https socket. Then we need to pass it to another process. We don't want to pass it through socket because of high load. Why we can't use shared memory or the same tricks you mention above to do it? > > > You don't want ssl? Omit ssl_handling_module in configuration! > > You don't want multiplexer? Omit it! > > Where's the difference from today ? Today it is very hard to do any changes in apache because it all in one. We can't insert multiplexer without breaking ssl or rewrite ssl code, as I see. > > > cu