> There are no plans for this. I looked at it for Apache 1.3 and there is > no clean way to do it. Yes, I know mod_perl can do it, but it is a very > very ugly hack. It may be easier and cleaner to do it for Apache 2.0. > Haven't looked at that yet. > Thanks Rasmus. If there's no clean way to do it, PHP is probably better off without it right now. I hope you'll have at it again some time when you have a moment.
Also thanks to Adam for his post on mod_vhost_alias. I'm aware of the module Adam, but it's not as flexible as PerlSections, which can be used to configure almost any aspect of the Apache server. This is particularly useful when dealing with hosting "plans" or even custom-configured hosting solutions. The client's VirtualHost config can be pulled from a relational database, which can of course be linked to the client themselves, and billing, etc. An intriguing concept that follows on from this is the storage of client configurations on a central database server. This would be very useful for a medium-large web hosting facility that wishes to offer custom configurations instead of plain ol' plans. Security would naturally be a concern, but if communications between machines were secured correctly, it should be quite interesting to play with on a machine running freeVSD. adam -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php
