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 (hermes.apache.org: domain of samisa.abeysinghe@gmail.com
 designates 64.233.184.197 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references;
        b=gT+F7umpUpssVPgv/loi/dUQEqU/gdss1ZdGE7RWXc+/c76wtnMhuGIlMHcSDorK+dQvIyZOA9dartXd2ttLyQLwC2BQnnfFNX7Wax1bJz7XRLk3Ur9LqKjVk5REzrE2PHqBDO+1MFotI1Zijd0DgWdBRRnh+GXCcrYh4kvVUys=
Message-ID: <a0f0c14804122103497caad522@mail.gmail.com>
Date: Tue, 21 Dec 2004 11:49:04 +0000
From: Samisa Abeysinghe <samisa.abeysinghe@gmail.com>
Reply-To: Samisa Abeysinghe <samisa.abeysinghe@gmail.com>
To: Apache AXIS C Developers List <axis-c-dev@ws.apache.org>
Subject: Re: 1.4 release still does not work with SSL channels.
In-Reply-To: <20041221082554.M32516@opensource.lk>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
References: <20041221082554.M32516@opensource.lk>

Re: For example both axis2 and axis2ssl contain whole of Axis2Transport.cpp etc.

I do not agree, I reuse the same class and build the transport lib to
be specified in axiscpp.conf.
This helped by making sure both ipv6 and ipv4 only trasports to live
side by side.

The problem with SSL trasport is to enable both channel and secure
channel based on the use of http or https. This could be easily done
by extending the channel class as I have done in IPV6 implemetation.

If one needs 2 SSL implementations be supported, one could build two
trasport libs and use them with the help of axiscpp.conf. It does not
matter if we load only the channel or the channel with the transport
logic, because we have to load two libs if we are to use two SSL
implementations any way.

Samisa...


On Tue, 21 Dec 2004 14:28:45 +0600, Damitha Kumarage
<damitha@opensource.lk> wrote:
> Hi Samisa,
> On Tue, 2004-12-21 at 13:23, Samisa Abeysinghe wrote:
> Re: I don't see this as a good solution.
> >
> > Why not? Any specific reasons ??
> > 
> Well,
> for ipv6 implementation we can see in Makefile.am you have hardcoded
> 
> SUBDIRS = ipv6 @SSLBUILD@
> 
> This means that when you build, it definitely go into ipv6 and build it.
> This may be ok with ipv6. But in case of SSL if we hard code like that
> then it will go and try to build it. This means that user need to have
> ssl specific header files included and libraries linked even if he don't need
> any ssl.
> 
> see below as well
> 
> > Samisa...
> 
> > -----Original Message-----
> > From: Damitha Kumarage [mailto:damitha@opensource.lk]
> > Sent: Tuesday, December 21, 2004 11:27 AM
> > To: Apache AXIS C Developers List
> > Subject: Re: 1.4 release still does not work with SSL channels.
> >
> > Has anyone looked into how IPV6 transport was done over axis2 transport?
> > Could we use the same for SSL transport?
> >
> > I think, the fact that we tried to make the SSL channel dynamically
> > lodable lead us into trouble
> >
> > - do you folks think that the way IPV6
> > was done is a solution to this (that is load the whole transport with
> > a differernt channel)?
> > 
> Does this mean that we keep another transport similar to axis2(for example
> named as axis2ssl)? then if user need ssl he load the whole of
> axis2ssl transport? I remember that in the very beginning of supporting ssl,
> we had the same idea. But later we abandoned the idea because of unneccessary
> redundancy of code that occur. For example both axis2 and axis2ssl contain
> whole of Axis2Transport.cpp etc.
> 
> thanks
> damitha
> 
>  Or is it too bad ;-)
> >
> > I don't see this as a good solution.
> >
> > Thanks,
> > Samisa...
> >
> >
> > On Mon, 20 Dec 2004 13:25:25 +0000, John Hawkins <HAWKINSJ@uk.ibm.com>
> > wrote:
> > >
> > >
> > > Dimitha - can you confirm that SSl does not work ?
> > >
> > > If so then we should put this fact on the website and delay support.
> > >
> > > It looks to me like we are discussing designing it again?
> > >
> > > John Hawkins
> > >
> > >             Fred
> > >             Preston/UK/IBM@IB
> > >             MGB
> > To
> > >                                       "'Apache AXIS C Developers
> > List'"
> > >             20/12/2004 13:09          <axis-c-dev@ws.apache.org>
> > >
> > cc
> > >
> > >             Please respond to
> > Subject
> > >              "Apache AXIS C           1.4 release still does not work
> > >             Developers List"          with SSL channels.
> > >
> > >
> > > Hi All,
> > >      I've just tried to use SSL in the 1.4 release and it still does
> > not
> > > work on Linux or Windows...  I'm in the process of coming up with a
> > model
> > > that will try to explain how I think the whole Channel/Transport area
> > > should be organised and will be looking for comment.  I hope to send
> > out a
> > > rough draft this afternoon.
> > >
> > > Regards,
> > >
> > > Fred Preston.
> > >
> > >
> 
> --
> Damitha Kumarage
> hSenid Software International (PVT) Ltd
> damitha@hSenid.lk
> 
> Lanka Software Foundation (http://www.opensource.lk)
> 
>