[EMAIL PROTECTED] wrote:
On Tue, 12 Mar 2002, jean-frederic clere wrote:
myworker1=
Would be the same as:
myworker1=ajp13://localhost:8009?lbfactor=0debug=ERROR
(no load balancing and only log error messages).
How to describe AF_UNIX or shared memory (as transport but not
[EMAIL PROTECTED] wrote:
On Tue, 12 Mar 2002, jean-frederic clere wrote:
What to do when myvhost is www.apache.org for example...
uri.www.apache.org:/examples.worker? Using ':' instead of '.' does not
solve the problem.
Sounds good.
If we use a hierarchical name we also solve
On Tue, 12 Mar 2002, jean-frederic clere wrote:
myworker1=
Would be the same as:
myworker1=ajp13://localhost:8009?lbfactor=0debug=ERROR
(no load balancing and only log error messages).
How to describe AF_UNIX or shared memory (as transport but not protocol)?
Even more extreme - use full uri, with query strings. We're in a http
server, we should know how to parse this kind of stuff :-)
Location /examples
JkUriSet worker
ajp13://tomcat_host.my.com:8009?lbfactor=10debug=INFO
/Location
Good, but Apache oriented
And another idea for
[EMAIL PROTECTED] wrote:
Yes, it's happening again... I feel I'm really close to
what I want - so please send feedback !
The goal - improve mod_jk2 configuration.
Subgoals:
- make it more intuitive / simpler / cleaner
- allow runtime changes ( and query )
The proposed solution:
Yes, it's happening again... I feel I'm really close to
what I want - so please send feedback !
Let's go
The goal - improve mod_jk2 configuration.
Subgoals:
- make it more intuitive / simpler / cleaner
- allow runtime changes ( and query )
good
The proposed solution:
Same config model
On Tue, 12 Mar 2002, GOMEZ Henri wrote:
but the config module will locate 'worker.ajp13' and
call setProperty(port, 8009 ).
You mean
the config module will locate 'worker.ajp13'
call getProperty(port, 8009 )
setProperty, yes.
The current impl ( not checked in ) adds a new struct,
Yes, it's happening again... I feel I'm really close to
what I want - so please send feedback !
The goal - improve mod_jk2 configuration.
Subgoals:
- make it more intuitive / simpler / cleaner
- allow runtime changes ( and query )
The proposed solution:
Same config model that is used in