You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Sharon Gowan <sg...@bbn.com> on 2004/09/10 15:29:08 UTC

Axis transport mechanisms??

Hi

I'm new to this list and apologize if this question is posted to the wrong 
place, ...but, here goes.

Where can I read about the transport layer used by Axis?  ...Is there an 
option between TCP and UDP?  Has anyone developed/tested Axis-based web 
services over a wireless network that has limited bandwidth?

Thx!


Re: Axis transport mechanisms??

Posted by Steve Loughran <st...@apache.org>.
Samuel Meder wrote:
> On Fri, 2004-09-10 at 09:36, Steve Loughran wrote:
> 
>>Sharon Gowan wrote:
>>
>>>Steve:
>>>
>>>Thanks for the quick response.  ...I have one followup.  As I 
>>>understand, HTTP1.0 can run over either UDP or TCP.  If we're developing 
>>>with Axis/Apache, is there a choice or is it always TCP?
>>
>>HTTP runs over TCP *only*. TCP is built on UDP.
> 
> 
> You mean IP, not UDP?
> 
> /Sam

yeah, you are right. TCP uses IP *datagrams*, which is what UDP also is 
built on -but UDP hides the fact less.

Re: Axis transport mechanisms??

Posted by Samuel Meder <me...@mcs.anl.gov>.
On Fri, 2004-09-10 at 09:36, Steve Loughran wrote:
> Sharon Gowan wrote:
> > Steve:
> > 
> > Thanks for the quick response.  ...I have one followup.  As I 
> > understand, HTTP1.0 can run over either UDP or TCP.  If we're developing 
> > with Axis/Apache, is there a choice or is it always TCP?
> 
> HTTP runs over TCP *only*. TCP is built on UDP.

You mean IP, not UDP?

/Sam
-- 
Sam Meder <me...@mcs.anl.gov>
The Globus Alliance - University of Chicago
630-252-1752



Re: Axis transport mechanisms??

Posted by Steve Loughran <st...@apache.org>.
Sharon Gowan wrote:
> Steve:
> 
> Thanks for the quick response.  ...I have one followup.  As I 
> understand, HTTP1.0 can run over either UDP or TCP.  If we're developing 
> with Axis/Apache, is there a choice or is it always TCP?

HTTP runs over TCP *only*. TCP is built on UDP.

Re: Axis transport mechanisms??

Posted by Sharon Gowan <sg...@bbn.com>.
Steve:

Thanks for the quick response.  ...I have one followup.  As I understand, 
HTTP1.0 can run over either UDP or TCP.  If we're developing with 
Axis/Apache, is there a choice or is it always TCP?

Thx again,

Sharon

At 09:50 AM 9/10/2004, Steve Loughran wrote:
>Sharon Gowan wrote:
>>Hi
>>I'm new to this list and apologize if this question is posted to the 
>>wrong place, ...but, here goes.
>>Where can I read about the transport layer used by Axis?  ...Is there an 
>>option between TCP and UDP?
>
>SOAP over UDP was only published as a specification last week, I'd be 
>surprised to see anything with it in. Axis only supports HTTP out the box, 
>though are free to add new transports.
>
>>Has anyone developed/tested Axis-based web services over a wireless 
>>network that has limited bandwidth?
>
>Axis's TCPmonitor can simulate connections with latency/limited bandwidth 
>to verify your code works over slow links.
>
>as with all HTTP1.0 connections, Nagling limits startup time, and without 
>keeping the connection open you dont get the full benefits of its 
>bandwidth adaptation. I dont know what the HTTP1.1 support is like.
>
>wireless networks also have interesting reliablity problems, but that is 
>out of our scope.
>
>-steve


Re: Axis transport mechanisms??

Posted by Steve Loughran <st...@apache.org>.
Sharon Gowan wrote:
> Hi
> 
> I'm new to this list and apologize if this question is posted to the 
> wrong place, ...but, here goes.
> 
> Where can I read about the transport layer used by Axis?  ...Is there an 
> option between TCP and UDP? 

SOAP over UDP was only published as a specification last week, I'd be 
surprised to see anything with it in. Axis only supports HTTP out the 
box, though are free to add new transports.

> Has anyone developed/tested Axis-based web 
> services over a wireless network that has limited bandwidth?

Axis's TCPmonitor can simulate connections with latency/limited 
bandwidth to verify your code works over slow links.

as with all HTTP1.0 connections, Nagling limits startup time, and 
without keeping the connection open you dont get the full benefits of 
its bandwidth adaptation. I dont know what the HTTP1.1 support is like.

wireless networks also have interesting reliablity problems, but that is 
out of our scope.

-steve