Mladen Turk wrote: > Hi, > > I would like to make a jk2.properties and workers2.properties as working > one by the installation. > Hope that I express myself as understandable :). > > This means that the default jk2 and workers2 properties should have only > the minimum configuration directives needed for connector to work. > My suggestion is that we use the channelSocket for that and get rid of > all other unneeded directives, cause all the rest should go into the > documentation and configuration examples that are allready there. > Other is that we build couple of working configurations for each > connector like workers2.properties.jni, workers2.properties.unx, etc..., > also as working configuration examples for user convenience. > > The reason that I choose the socket connector as default one is that the > TC is generally installed that way, so hopefully we'll have a working > connector following only the basic installation steps. > > Further more the configuration should IMO have the TC and connector > documentation mapped. > So, I would like to here other peoples thoughts about that.
+1 Less configuration files less problems and users reports... -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
