Re: new modules in trunk
On 1 Dec 2008, at 08:17, Paul Querna wrote: I've committed a few new modules to trunk tonight: Interesting. Are we expecting docs anytime soon? -- Nick Kew
Re: new modules in trunk
On Mon, Dec 1, 2008 at 11:17 AM, Paul Querna [EMAIL PROTECTED] wrote: mod_heartmonitor: Collects these Multicast heartbeats for other modules to use. Interesting. Is there other modules that create separate thread(s) for bypassing request-response thing? -- С уважением, Кевац Марко Sincerely yours, Kevac Marko
Re: new modules in trunk
Nick Kew wrote: On 1 Dec 2008, at 08:17, Paul Querna wrote: I've committed a few new modules to trunk tonight: Interesting. Are we expecting docs anytime soon? patches welcome, the reademe files aer all I really had :-)
Re: new modules in trunk
Den Monday 01 December 2008 09:17:24 skrev Paul Querna: I've committed a few new modules to trunk tonight: mod_ratelimit: Bandwidth Rate Limiting for Clients. mod_heartbeat: Generates Multicast heartbeat messages containing the status of the server. mod_heartmonitor: Collects these Multicast heartbeats for other modules to use. mod_lbmethod_heartbeat: Module to Load Balance mod_proxy_balancer workers using the data from the heartbeats. If people could take a closer look at mod_lbmethod_heartbeat especially, since it is completely new, and I don't really know the internals of mod_proxy that well, while the other ones are a little more battle tested. Thanks, Paul Apache 2.2.10 segfaults if either/or mod_heartbeat/mod_heartmonitor is unconfigured and/or has no access to the logs directory. Hard to say in which combination. Well..., heh..., I wanted to try this on Mandriva. When configured and has access to the logs directory it does not segfault. Just thought I should mention this despite the modules is from trunk. -- Regards // Oden Eriksson
Re: new modules in trunk
Kevac Marko wrote: On Mon, Dec 1, 2008 at 11:17 AM, Paul Querna [EMAIL PROTECTED] wrote: mod_heartmonitor: Collects these Multicast heartbeats for other modules to use. Interesting. Is there other modules that create separate thread(s) for bypassing request-response thing? Considered doing this for the data vs. control channel of mod_ftp, but it's essentially not necessary and introduces additional overhead to set up and tear down threads during operation. A thread pool was an alternative, but in the end, it looked too expensive to consider.
Re: new modules in trunk
William A. Rowe, Jr. wrote: Kevac Marko wrote: On Mon, Dec 1, 2008 at 11:17 AM, Paul Querna [EMAIL PROTECTED] wrote: mod_heartmonitor: Collects these Multicast heartbeats for other modules to use. Interesting. Is there other modules that create separate thread(s) for bypassing request-response thing? Considered doing this for the data vs. control channel of mod_ftp, but it's essentially not necessary and introduces additional overhead to set up and tear down threads during operation. A thread pool was an alternative, but in the end, it looked too expensive to consider. For beartbeat/heartmonitor, originally, I wrote them to spawn a thread off the master process, but code running as root sucks, and if there were any problems like it crashing, it would fubar up the entire httpd process chain. Later I moved it to using a thread on each worker process, since if it crashes, I still have other workers, and now the code is running in the child without privileges. If the core fully supported UDP and multicast listeners, it should be possible to write the heartmonitor module as just a protocol module, although heartbeat would still likely need its current structure. -Paul
Re: new modules in trunk
Paul Querna wrote: ... If the core fully supported UDP and multicast listeners, it should be possible to write the heartmonitor module as just a protocol module, although heartbeat would still likely need its current structure. ... Issac Goldstand already developed UDP support, for the contributed mod_dns (both financed by my company, and contributed to the ASF). I believe that it's finally the time to add these things (together with mod_ftp) officially to the trunk, at least as experimental. Their place is there, and as low level modules, it's much more native to include them than some of mentioned modules. The current server, which was an HTTP daemon in the past, already supports various protocols (HTTPS, FTP in the proxy, etc.), si FTP and DNS will be great, especially when it's so hard to support them as external modules, contrary to some of the mentioned modules. Adding the SMTP module (as experimental, because it still needs many fixes) may close the circle and makes APACHE an all-in-one server, when many features (such as buckets-brigades, configuration, pools, MPM's, etc.) are reused in all of the protocols, and make APACHE a very elegant and smart server. -- Eli Marmor [EMAIL PROTECTED] CEO, Netmask (El-Mar) Internet Technologies Ltd. __ Tel.: +972-9-766-1020 8 Yad-Harutzim St. Fax.: +972-9-766-1314 P.O.B. 7004 Mobile: +972-50-5237338 Kfar-Saba 44641, Israel
