Hi, I implemented the changes we discussed, now mod_jk2 supports only 2 spache specific directives - JkSet ( fully equivalent with workers.properties ), and JkUriSet for per/location settings.
The big problem is urimap.properties. The file is used for IIS, and is equivalent with JkMount. JkMount /uri worker is /uri=worker What we need is a bit more power - to specify other per/dir properties ( some needed for mapper to avoid duplicated mapping, some for features ). We also need to make place for the vhost. My proposals: 1) Name the 'main' file jk2.properties ( instead of workers.properties, since it does more than workers ). Name the mapping file jkmap.properties ( or jkuri ? ) 2) New syntax for uri properties. uri.[PROPERTY_NAME]:[host][port]/[path]=value This is similar with worker.NAME.PROPERTY_NAME=value, however for paths this is a bit ugly. Obviously, a good solution would be to use XML, but I don't feel ready to do XML in C for this release of jk. Also, the file will be generated - and not visible to most users. 3) Multiple config files are already supported. I would like to have one jkmap.properties for each webapp. We can either use a single dir, conf/jk/apps and have a file per webapp - using names like APPNAME.jkmap. Or we can have it as WEB-INF/jkmap.properties. The file will contain all mappings for a webapp. If an app is added or reloaded, only those mappings will have to change - that will help a lot in allowing app changes without restarting the web server. 4) Same thing for workers. I would like a separate config file per worker. If loadbalancing is used, you can just add the worker.jkworker to conf/jk/workers and tell mod_jk to read it. It'll also be cleaner. Those are just some ideas - 2 is the important one. Opinions ? Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
