axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <samisa.abeysin...@gmail.com>
Subject Re: [Axis2] TCP transport build should be optional?
Date Tue, 24 Jul 2007 02:15:07 GMT
Dinesh Premalal wrote:
> Samisa Abeysinghe <samisa@wso2.com> writes:
>
>   
>> By default the tcp server builds. The chances are more people would be
>> interested in HTTP. 
>>     
> To be accurate, Both HTTP and TCP transports build by default. 
>   
>> Would it be a good idea to switch off building TCP
>> transport by default?
>>     
> Although TCP transport builds , axis2/c use HTTP transport by
> default. Therefor our normal behavior doesn't change.If someone need 
> to activate TCP transport , then he should need to add
> axis2_tcp_sender to axis2.xml 
>
> Plus point of having TCP transport build by default is, user will be 
> able to use it at any time he wish. (don't need to give options and 
> compile). We wouldn't need to give options to enable TCP transport
> because it doesn't require any additional libraries or dependencies.
>
> My understanding is, though TCP transport build by default, it doesn't 
> do any harm :), And both HTTP and TCP would be able to coexist.
>   
Bulk of the users want http, so why should they wait till tcp to build?
Also, when embedding, I just want http, and I want to disable tcp, so it 
helps to be able to disable building tcp.

Samisa...


-- 
Samisa Abeysinghe : http://people.apache.org/~samisa/


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org


Mime
View raw message