On Feb 6, 2009, at 12:17 AM, Brian McCallister wrote:
* VMs are attached to apr pools.
+1
* Concurrency is up to the client
What are you defining as "the client"?
We should not expose configuration options which will create
concurrency issues, such as attaching a VM to the server_re
On Feb 11, 2009, at 6:22 PM, Graham Leggett wrote:
Would it make sense for mod_memcache to become a provider beneath
mod_socache, or am I missing something?
mod_memcache really just provides the config "glue" for apr_memcache
so that every module that wants to use apr_memcache doesn't hav
On Mar 5, 2009, at 4:35 PM, Kevac Marko wrote:
ise.
mod_memcache, if we are talking about
http://code.google.com/p/modmemcache/, is too simple.
Works fine for me :)
I need multiple name pools to multiple servers. Something like
Will you implement a "default" pool like mod_dbd does?
T
On Mar 5, 2009, at 4:52 PM, Kevac Marko wrote:
80 columns is a little bit ancient requirement in the world of 22"
LCDs, but ok, i'll fix that too.
Not when you have 4 code branches side by side...
Also, netbooks are pretty popular as well. Most of my coding is done
on a 15" laptop screen.
On Mar 6, 2009, at 1:25 AM, Kevac Marko wrote:
And after that you have to restart apache? It's not enough dynamic
for us.
graceful restart.
On Mar 28, 2009, at 11:09 AM, Paul Querna wrote:
- Much simpler configuration than mod_proxy, using location blocks
(or locationMatch), rather than ProxyPass' hacking of URI stuff way
earlier.
It'd be nice to be able to configure and do stuff at run time using Lua.
Someone had to ask...
-
On Mar 30, 2009, at 7:37 PM, Paul Querna wrote:
mod_watchdog is the latest offender in a series of modules that expose
additional functions to the API. (mod_proxy and mod_cache do too!)
What happened to all functions that are not inside server/* must be
either dynamic optional functions or hoo
