-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Atif Ghaffar schreef: >> I like this idea. Can we make it a configuaration option / or a separate >> handler. > >> It would work in my case for example I will know that there are always >> max 10/100/1000 connections open to the DB no matter what. >> Everything else will fail in other layers. > >> This way when I know that I must upgrade the DB to handle 100 instead of >> 10 connections it could be justified. > > >> For example if there is a complain "App is too slow" then instead of >> throwing hardware on it, we can figure out where it is slowing down. >> Imagine this. A careless application might use DB for session storage. A >> DDOS on just that website will bring down the DB. Thats just silly.
http://repo.or.cz/w/handlerosm.git?a=blob;f=handler_osm.c;h=2b4ac855a8d3eea4e69af1e9e6c587a6ab03bf9e;hb=HEAD Look for the section ifdef pooling. I think we could implement this in dbslayer too. But I kinda want to have a more abstract dbslayer before I get into this development. I already have a patch for more database in dbslayer, but that is also based on the assumption that you connect for each request. Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREKAAYFAkrSCIYACgkQYH1+F2Rqwn3pEgCfb7xN8XCOCQDRRw5Ayh2vufXK rJsAnjIhECtZ2p7bG+IiWvZPLIcZfXGi =G76b -----END PGP SIGNATURE----- _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
