Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 64689 invoked from network); 26 Oct 2005 15:17:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Oct 2005 15:17:54 -0000 Received: (qmail 52865 invoked by uid 500); 26 Oct 2005 15:17:54 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 52830 invoked by uid 500); 26 Oct 2005 15:17:53 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 52819 invoked by uid 99); 26 Oct 2005 15:17:53 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Oct 2005 08:17:53 -0700 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of PRESTONF@uk.ibm.com designates 195.212.29.137 as permitted sender) Received: from [195.212.29.137] (HELO mtagate4.uk.ibm.com) (195.212.29.137) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 26 Oct 2005 08:17:51 -0700 Received: from d06nrmr1407.portsmouth.uk.ibm.com (d06nrmr1407.portsmouth.uk.ibm.com [9.149.38.185]) by mtagate4.uk.ibm.com (8.12.10/8.12.10) with ESMTP id j9QFHU34028380 for ; Wed, 26 Oct 2005 15:17:30 GMT Received: from d06av04.portsmouth.uk.ibm.com (d06av04.portsmouth.uk.ibm.com [9.149.37.216]) by d06nrmr1407.portsmouth.uk.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j9QFHUSs196250 for ; Wed, 26 Oct 2005 16:17:30 +0100 Received: from d06av04.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.13.3) with ESMTP id j9QFHU8p008900 for ; Wed, 26 Oct 2005 16:17:30 +0100 Received: from d06ml068.portsmouth.uk.ibm.com (d06ml068.portsmouth.uk.ibm.com [9.149.38.194]) by d06av04.portsmouth.uk.ibm.com (8.12.11/8.12.11) with ESMTP id j9QFHUv5008894 for ; Wed, 26 Oct 2005 16:17:30 +0100 In-Reply-To: To: "Apache AXIS C Developers List" MIME-Version: 1.0 Subject: Re: HTTPTransport X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 Message-ID: From: Fred Preston Date: Wed, 26 Oct 2005 16:17:29 +0100 X-MIMETrack: Serialize by Router on D06ML068/06/M/IBM(Release 6.53HF247 | January 6, 2005) at 26/10/2005 16:17:29, Serialize complete at 26/10/2005 16:17:29 Content-Type: multipart/alternative; boundary="=_alternative 0053FFBC802570A6_=" X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N This is a multipart message in MIME format. --=_alternative 0053FFBC802570A6_= Content-Type: text/plain; charset="US-ASCII" Hi Chris, The Transport uses HTTPChannel which actually does all the communication work of opening, sending/receiving and closing the socket. The Transport layer is supposed to be removed/abstracted from the actual physical acts of opening a socket, etc. and is only responsible for managing these acts. Depending on the action, you will see that the amount of interaction differs. In reality, it is more tightly bound to a http sort of transport, so it should be renamed HTTPTransport, but that's another matter! Regards, Fred Preston. "Christopher S. Johnson" 26/10/2005 14:47 Please respond to "Apache AXIS C Developers List" To: axis-c-dev@ws.apache.org cc: Subject: HTTPTransport All - New to axis c but not new to axis, just a quick question so I can better understand how to build my own transport, I'm sure I'll have more later :) is the transport module is actually responsible for sending the bytes, in turn opening the real connection and reading and writing from the socket? everything is abstracted out so nice it makes it a bit confusing.. how ironic :) Thanks ..Chris --=_alternative 0053FFBC802570A6_= Content-Type: text/html; charset="US-ASCII"
Hi Chris,
        The Transport uses HTTPChannel which actually does all the communication work of opening, sending/receiving and closing the socket.  The Transport layer is supposed to be removed/abstracted from the actual physical acts of opening a socket, etc. and is only responsible for managing these acts.  Depending on the action, you will see that the amount of interaction differs.  In reality, it is more tightly bound to a http sort of transport, so it should be renamed HTTPTransport, but that's another matter!

Regards,

Fred Preston.


"Christopher S. Johnson" <johnsocs@clarkson.edu>

26/10/2005 14:47
Please respond to "Apache AXIS C Developers List"

       
        To:        axis-c-dev@ws.apache.org
        cc:        
        Subject:        HTTPTransport

       


All -

New to axis c but not new to axis, just a quick question so I can better
understand how to build my own transport, I'm sure I'll have more later :)

is the transport module is actually responsible for sending the bytes, in
turn opening the real connection and reading and writing from the socket?

everything is abstracted out so nice it makes it a bit confusing.. how
ironic :)

Thanks
..Chris
--=_alternative 0053FFBC802570A6_=--