>> I can see that this is going to make life difficult for
>ApacheConfig. Yes,
>> hopefully we can deprecate it soon. But in the mean time,
>I'd personally
>> prefer that the port is a property of the worker.ajp13. So
>your example
>> would be:
>> worker.ajp13.channel=socket
>> worker.ajp13.port=8009
could we use for example
worker.ajp13.channel=socket,8009
worker.ajp13.channel=unix,path
a channel know from first arg, the revelant next args.
a socket need a listen port, a unix domain socket need path
>Right now there's no 'magic' in jk2, but as soon as things are stable
>I'll start adding it - setting the port on the worker is easy, and
>more.
>
>If we use a new default name ( jk2.properties ? ) and
>default location ( ${ServerRoot}/conf/jk2.properties ), the only
>change in httpd.conf will be including mod_jk.so ( and we can
> clearly recommend puting mod_jk.so in modules/,
>like all other modules )
yes, that's the way it works today in my rpms...
>There's a small problem here. If you use a management application
>or ajp14 to automatically deploy apps - the config file will
>change on disk. If you edit it manually at the same time - not
>good :-).
we may add a directive from preventing automatic deployment ?
>You can continue to edit it manually, and it's easy to code
>something in the status ( or conf ) worker to reload jk2.properties
>gracefully - without even restarting the server. ( you don't
>want to restart apache every time a worker is added/removed ).
>I would rather spend the time writing a jk_config_ldap - that would
>much more sense given the target ( farms of workers and servers, etc ).
>But that would require more work on tomcat as well to make it get
>config from a directory service ( quite easy to do, if we had time ).
Good idea that ldap ;)
>Propeties are good as 'common ground' because they force us to
>keep things simple. As soon as we add XML, people may use entities,
>includes, etc.
Agreed, ok for properties for now.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
