Hi Ajith, We enabled thrift as default key validation type because it faster than WS client(its fast compare to web service call as data transfer happens on tcp level). Usually default configurations focused on performance and then first time experience(default product without config changes) would be nice.
Thanks, sanjeewa. On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana <[email protected]> wrote: > Hi All, > > Most of the time we deploy the AM as a distributed cluster and we can't > use thrift for key validations. So our recommendation to use WSClient > instead of thrift. Therefore it is better to keep the default configuration > with WSClient and disable thrift, using that we can deduce the a > configurations step. The advance is configuring the so many instances. > > <KeyValidatorClientType>*WSClient*</KeyValidatorClientType> > <ThriftClientPort>10397</ThriftClientPort> > > <ThriftClientConnectionTimeOut>10000</ThriftClientConnectionTimeOut> > <ThriftServerPort>10397</ThriftServerPort> > <!--ThriftServerHost>localhost</ThriftServerHost--> > <EnableThriftServer>*false*</EnableThriftServer> > > WDYT ? > > Thanks. > Ajith > > > -- > Ajith Vitharana. > WSO2 Inc. - http://wso2.org > Email : [email protected] > Mobile : +94772217350 > > -- *Sanjeewa Malalgoda* WSO2 Inc. Mobile : +94713068779 <http://sanjeewamalalgoda.blogspot.com/>blog :http://sanjeewamalalgoda.blogspot.com/ <http://sanjeewamalalgoda.blogspot.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
