On Wed, 20 Mar 2002, GOMEZ Henri wrote: > could we use for example > > worker.ajp13.channel=socket,8009 > worker.ajp13.channel=unix,path
The problem is that the communication channel and the protocol are distinct entities. You can add a new channel with it's own properties ( like JNI, or windows specific, or pipes, or message queues ) and that shouldn't require changes in the the worker setup - the worker doesn't care how the msg is actually sent. For socket - it's easy to include the magic so that worker.ajp13.port=8009 will automatically create the socket. It's also easy to include .path or any other property, with the associated magic. But the 'canonical' setting, which allows arbitrary channels and properties - should be with separated objects. Example: you can have a channel.socket.debug=1 channel.socket.soTimeout=100 ... worker.ajp13.debug=0, Putting all the channel options in magic worker properties is very painfull. > >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 ? We must first add the code to _allow_ automatic deployment :-) ( or just run-time deployment and configuration ). Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
