> > 1. JkSet NAME VALUE > Will have exactly the same behavior as NAME=VALUE in a > workers.properties file. > All settings that you can do in workers.properties today > could be done by JkSet, in httpd.conf. Or all settings > could be done in workers.properties. > > For example JkLogLevel DEBUG will be now: > JkSet logLevel DEBUG ( in httpd.conf ) > or > logLevel=DEBUG ( in workers.propertes ) > > The first style is for people who prefer working with > httpd.conf, the other one will be easier for IIS/iPlanet > and may be easier to generate/edit. >
+1 - i really like the idea of being able to configure the different web servers +(apache/iis/netscape) in a similar fashion. > 2. JkWebapp NAME VALUE > Set properties on a webapp level. Will be set > at <Location> level. An equivalent setting will be > in a uri-workers.properties ( or a better named one ), > the same that we use for IIS. > > JkMount is not doing anything special - it's the same > efect as the properties file we use on IIS. Except that > properties are easier to generate and will be consistent > for all servers ( no longer need to generate 3 different > styles ). > > <Location> will be used for performance, it uses > the apache mapper instead of jk's. > +1 for the same reasons as above. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
