[EMAIL PROTECTED] wrote: > > On Tue, 12 Mar 2002, jean-frederic clere wrote: > > > myworker1= > > Would be the same as: > > myworker1=ajp13://localhost:8009?lbfactor=0&debug=ERROR > > (no load balancing and only log error messages). > > > > How to describe AF_UNIX or shared memory (as transport but not protocol)? > > myworker1=ajp13://file_name:afsocket?lbfactor=0&debug=ERROR > > myworker1=ajp13://key_file:shm?lbfactor=0&debug=ERROR > > Good question... > > ajp13:aprChannel:/tmp/tomcat.socket?.... > or > apj13:channel.apr:/tmp/tomcat.socket?lbfactor=0... > > ajp13:jniChannel?lbfactor=0&debug=0 > > If no channel is specified, default to the socket channel. > ajp13:channel.socket://localhost:8009 > ajp13://localhost:8009 > > Ok, so the question is: which form ? The goal is to be intuitive, easy to > type, easy to explain. It seems some hierarchical naming is the best way > ( but which form ? ). > > So far we have the following: > > - separators do not matter ( syntactical sugar ) - . : / _ - > - each 'name' is hierarchical > - a name with a single component ( myworker1 ) defines an alias, for > easier typing. The RHS will be the real name. Question: should it be > alias.myworker1=ajp13://.... ?
Why do we alias? > > - The first part of the hierarchical name will identify the type. > > - The second part of the hierarchical name be used by the constructor. > For example, the ajp13 constructor will take the local part and interpret > the first component as a channel name, then what's after ? as parameters. > > What do we do about properties ? Are we going with 2 styles - a URL style > and a workers.properties style ? No... We should choose one. > > In workers.properties style: > > ajp13.[LOCAL_PART].port=8009 > ajp13.[LOCAL_PART].debug=0 > ajp13.[LOCAL_PART].lbfactor=1 > > More ideas ? Implementing this is not trivial, but I would hate to have to > do it again. > > Costin > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
