Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Received-SPF: pass (herse.apache.org: domain of samisa.abeysinghe@gmail.com
 designates 64.233.162.225 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding;
        b=XHC4BzLp2w5ktyf/QWxYRmqRoXdvbVVMCPisGZeYhTNJ6RkhrzCF+9+nJsyNu43wV4twoxmEpeNuuH4krPxGCOUec97NveRgHNK1fRn4fyheaBXpM+V0ZSQwPNyjrLWhbnVpGb0JUbtt5B8kGWDys71i0hDeK5786Qq12DZXKUs=
Message-ID: <46A560AB.7040009@gmail.com>
Date: Tue, 24 Jul 2007 08:15:07 +0600
From: Samisa Abeysinghe <samisa.abeysinghe@gmail.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org>
Subject: Re: [Axis2] TCP transport build should be optional?
References: <46A40573.4010803@wso2.com> <87ejizeop4.fsf@etch.wso2.com>
In-Reply-To: <87ejizeop4.fsf@etch.wso2.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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