>> channel.socket.local.type=ajp13 ? > >No :-) > >The only protocol that we support in Jk at this moment is the >ajp13 protocol ( lb, status, etc are workers, but not protocols ), >so it is the default and users don't have to set it explicitely. > >I documented 2 properties, to be used to override the default >when new protocols/apis are added: > > channel.socket.local.protocol=ajp13 ( it could be WARP, or IIOP or RPC )
ok, that's what I looked for > channel.socket.local.api=ajp13 ( api means the methods that are >supported/used - it'll be ajp14, mod_webapp, etc ). do you mean we could have webapp APIs over ajp13 ? >Note that 'type' is as confusing as 'ajp13' - there are 3 things >here, a transport channel, a wire/marshalling/rpc protocol and >an actual API on top of the RPC protocol. > >Ajp14 can be a set of new functions ( i.e. an API ) that will >work on top of the same AJP13 RPC protocol. We really need >to distinguish between them and maybe find a better name for >the API ( or protocol ). Yes, protocol indicate how to transport infos, apis how to works/deal with them ;) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
