Re: [Dev] Optimize the configurations in api-manager.xml

2014-06-12 Thread Sumedha Rubasinghe
We recommend it where network level restrictions are there for Thrift.
WSClient only requires HTTP level access, where as for Thrift it's a new
port. Thrift, if done correct can reach far more concurrency.



On Thu, Jun 12, 2014 at 8:06 PM, Ajith Vitharana  wrote:

>
> Hi Sumedha,
>
> On Thu, Jun 12, 2014 at 7:53 PM, Sumedha Rubasinghe 
> wrote:
>
>> But normal practice is to have the best possible configuration as the
>> default one.
>>
>
> Why WSClient is not best for default, even we recommended it for
> production ?
>
> Thanks
> Ajith.
>
>
>>
>>
>> On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana  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.
>>>
>>>*WSClient*
>>> 10397
>>>
>>> 1
>>> 10397
>>> 
>>> *false*
>>>
>>> WDYT ?
>>>
>>> Thanks.
>>> Ajith
>>>
>>>
>>> --
>>> Ajith Vitharana.
>>> WSO2 Inc. - http://wso2.org
>>> Email  :  aji...@wso2.com
>>> Mobile : +94772217350
>>>
>>>
>>
>>
>> --
>> /sumedha
>> m: +94 773017743
>> b :  bit.ly/sumedha
>>
>
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Optimize the configurations in api-manager.xml

2014-06-12 Thread Sanjeewa Malalgoda
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  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.
>
>*WSClient*
> 10397
>
> 1
> 10397
> 
> *false*
>
> WDYT ?
>
> Thanks.
> Ajith
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>


-- 

*Sanjeewa Malalgoda*
WSO2 Inc.
Mobile : +94713068779

 blog
:http://sanjeewamalalgoda.blogspot.com/

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Optimize the configurations in api-manager.xml

2014-06-12 Thread Ajith Vitharana
Hi Sumedha,

On Thu, Jun 12, 2014 at 7:53 PM, Sumedha Rubasinghe 
wrote:

> But normal practice is to have the best possible configuration as the
> default one.
>

Why WSClient is not best for default, even we recommended it for production
?

Thanks
Ajith.


>
>
> On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana  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.
>>
>>*WSClient*
>> 10397
>>
>> 1
>> 10397
>> 
>> *false*
>>
>> WDYT ?
>>
>> Thanks.
>> Ajith
>>
>>
>> --
>> Ajith Vitharana.
>> WSO2 Inc. - http://wso2.org
>> Email  :  aji...@wso2.com
>> Mobile : +94772217350
>>
>>
>
>
> --
> /sumedha
> m: +94 773017743
> b :  bit.ly/sumedha
>



-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Optimize the configurations in api-manager.xml

2014-06-12 Thread Ajith Vitharana
On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana  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.
>

advance/advantage*


>
>*WSClient*
> 10397
>
> 1
> 10397
> 
> *false*
>
> WDYT ?
>
> Thanks.
> Ajith
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>


-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


Re: [Dev] Optimize the configurations in api-manager.xml

2014-06-12 Thread Sumedha Rubasinghe
But normal practice is to have the best possible configuration as the
default one.


On Thu, Jun 12, 2014 at 7:51 PM, Ajith Vitharana  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.
>
>*WSClient*
> 10397
>
> 1
> 10397
> 
> *false*
>
> WDYT ?
>
> Thanks.
> Ajith
>
>
> --
> Ajith Vitharana.
> WSO2 Inc. - http://wso2.org
> Email  :  aji...@wso2.com
> Mobile : +94772217350
>
>


-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev


[Dev] Optimize the configurations in api-manager.xml

2014-06-12 Thread Ajith Vitharana
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.

   *WSClient*
10397
1
10397

*false*

WDYT ?

Thanks.
Ajith


-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev