axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@opensource.lk>
Subject Re: Implementation of SOAPTransport interface using LibWWW for client
Date Tue, 03 Aug 2004 04:31:37 GMT
+1 for using -I and -L properly ..

Sanjiva.

----- Original Message ----- 
From: "John Hawkins" <HAWKINSJ@uk.ibm.com>
To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Sent: Monday, August 02, 2004 2:23 PM
Subject: Re: Implementation of SOAPTransport interface using LibWWW for
client


>
>
>
> I agree with  all your points :-) Not sure about the licencing but you're
> right - it can be got around.
>
> John Hawkins
>
>
>
>
>
>              Samisa Abeysinghe
>              <samisa_abeysingh
>              e@yahoo.com>                                               To
>                                        Apache AXIS C Developers List
>              02/08/2004 04:24          <axis-c-dev@ws.apache.org>
>                                                                         cc
>
>              Please respond to                                     Subject
>               "Apache AXIS C           Re: Implementation of SOAPTransport
>              Developers List"          interface using LibWWW for
>                                        client
>
>
>
>
>
>
>
>
>
>
> Hi All,
>    Few thoughts.
>    Copying LibWWW headers into cvs head would have licencing issues. Or
> would it not?
>    With transport abtraction layer the idea is to let the users select
> between transports. Hence I
> do not think it is a good idea to ship the headers for different trasport
> implementations with
> Axis C++ source.
>
>    Given a perticular transport, it is a good idea to stick to a given
> version of third party
> libs.
>
>    We could keep the headers(libs) where ever they are, without copying,
> and use '-I' ('-L')
> compiler options.
>    On Linux, need to copy headers is eliminated this way. I think for
> windows the same could be
> done.
> Thanks,
> Samisa...
>
> --- John Hawkins <HAWKINSJ@uk.ibm.com> wrote:
>
> >
> >
> >
> >
> > Hello,
> >
> > Hmm, we are talking about build here right - so where does install come
> > into it? Oh, I think I see - we seem to be mixing up build and install.
> > They are very different things for most "production" users - I'll try to
> be
> > explicit when I discuss these things.
> >
> > Re building axis libwww support - For things like the header files being
> > placed in src/transport/libwww etc. - can't we just put those header
> files
> > into our build in that directory permanently? I assume we would only
like
> > to support a particular version of libwww at any one time (given libwww
> is
> > very stable and header files don't change much)
> >
> > The lib files are more problematic of course, we could take the
viewpoint
> > that we are only supporting a particular version? It would be much
easier
> > to build that way but it means we would have to have a copy of the
libwww
> > libs created once and then updated (although libwww in this case hasn't
> > changed in a long time).
> >
> > cheers,
> > John.
> >
> >
> >
> >
> >
> >
> >
> >
>
> >              damitha kumarage
>
> >              <damitha@opensour
>
> >              ce.lk>
> To
> >                                        Apache AXIS C Developers List
>
> >              29/07/2004 12:40          <axis-c-dev@ws.apache.org>
>
> >
> cc
> >
>
> >              Please respond to
> Subject
> >               "Apache AXIS C           Re: Implementation of
> SOAPTransport
> >              Developers List"          interface using LibWWW for
>
> >                                        client
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >
> >
> >
> >
> > Hi Lahiru,
> >
> > This seems to be a very exhaustive list compared to the linux libwww
> > guide sent by Samisa(see further below).
> > I think lot of people are interested on an easier Windows build as well.
> > Can't we use a good opensource installer program to have a simpler Axis
> > C++ installation on Windows?
> >
> > thanks
> > damitha
> >
> > On Thu, 2004-07-29 at 17:12, lahiru@opensource.lk wrote:
> > > For Windows
> > >
> > > 1.Install libwww.
> > > 2.Copy the source header files in libwww which are in library/src to
> the
> > > c/src/transport/libwww.
> > > 3.copy the external header files in libwww which are in
> library/external
> > > to c/include/libwww.
> > > 4.copy the library files which are created while building the libwww
to
> >
> > > c/lib/libwww
> > > 5.Copy the gnu_regx.dll to path from libwww.
> > > 6.Build the AxisTransportLibwww VC project.
> > > 7.Copy the generated AxisTransport.dll to path
> > > 8.then run the samples.
> > >
> > > I included these informations to the readme file and diff is attached.
> > >
> > >
> > > Lahiru Wimalasiri
> > >
> > >
> > > > For Linux, I have explained this in the readme.txt in
> > > > src/transport/libwww/readme.txt
> > > >
> > > > Simply what you have to do is
> > > > 1. install LibWWW,
> > > > 2. build Axis C++ with libWWW support and
> > > > 3. set
> > > > Transport_http:[AXISCPP_DEPLOY]/lib/libaxis_LibWWWTransport.so
> > > > in axiscpp.conf.
> > > >
> > > > Samisa...
> > > >
> > > > --- damitha kumarage <damitha@opensource.lk> wrote:
> > > >
> > > >> Hi Lahiru,
> > > >> Is there any documentation how to use libwww as cleint transport?
> > > >> thanks
> > > >> damitha
> > > >> On Fri, 2004-07-23 at 16:43, lahiru@opensource.lk wrote:
> > > >> > Hi all,
> > > >> >
> > > >> >     I have crated the project files for Libwww on windows. Those
> > files
> > > >> are
> > > >> > attached with this.
> > > >> >
> > > >> > Lahiru
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >> > > --- lahiru@opensource.lk wrote:
> > > >> >
> > > >> > >> Hi All,
> > > >> > >>
> > > >> > >>   I have tested it on windows. all the samples are working
on
> > > >> windows.
> > > >> > >> But
> > > >> > >> it seems considerably slow.
> > > >> > >
> > > >> > > The slowness comes because of the use of 100-continue. On
Linux
> I
> > > >> could
> > > >> > > build LibWWW with
> > > >> > > --with-extension option and make it faster. I think a similar
> > option
> > > >> would
> > > >> > > be available for
> > > >> > > Windows that enables extentions, that makes non 100-continue
> > > >> requests
> > > >> > > possible.
> > > >> > >
> > > >> > > Thanks,
> > > >> > > Samisa...
> > > >> > >
> > > >> > >>
> > > >> > >> Lahiru Wimalasiri
> > > >> > >>
> > > >> > >>
> > > >> > >> >
> > > >> > >> > Hi All,
> > > >> > >> >
> > > >> > >> > I developed a transport module for clients using
the
trasport
> > > >> > >> abstraction.
> > > >> > >> > I tested it on Linux and all seems to be fine except
thread
> > > >> safety.
> > > >> > >> The
> > > >> > >> > module need to be tested on WIndows.
> > > >> > >> >
> > > >> > >> > The Axis C++ server side fails to work with 100-continue.
> Axis
> > > >> Java is
> > > >> > >> > capable of managing 100-continue. This is the default
mode
> used
> > > >> in
> > > >> > >> LibWWW.
> > > >> > >> > I used a macro in Makefile.am to enable/disable
100-continue.
> > > >> (use
> > > >> > >> > -DHT_EXT_CONTINUE to enable or -UHT_EXT_CONTINUE
to disable
> in
> > > >> > >> AM_CPPFLAGS
> > > >> > >> > setting) I observed that the transport is much
faster when
it
> > is
> > > >> used
> > > >> > >> > without 100-continue. However, to disable 100-continue,
> LibWWW
> > > >> need to
> > > >> > >> be
> > > >> > >> > built with -with-extension option (./configure
> > --with-extension)
> > > >> > >> >
> > > >> > >> > You do not need to bother about location of LibWWW
headers
> and
> > > >> > >> libraries,
> > > >> > >> > provided that you have done the LibWWW installation
properly.
> I
> > > >> have
> > > >> > >> used
> > > >> > >> > libwww-config in the Makefile.am to pick LibWWW
specific
> > > >> settings.
> > > >> > >> >
> > > >> > >> > Once you build the library, you could use it by
specifying
> the
> > > >> > >> location of
> > > >> > >> > the lib in $AXIS_HOME/axiscpp.conf file.
> > > >> > >> >
> > > >> > >> >
> > e.g.Transport_http:/usr/local/Axis/libs/libaxis_LibWWWTransport.so
> > > >> > >> >
> > > >> > >> > For more information on LibWWW please see
> > > >> > >> http://www.w3.org/Library/User/
> > > >> > >> >
> > > >> > >> > Issues:
> > > >> > >> >
> > > >> > >> > The thread test in tests/client/threadSafe fails
with this
> > > >> > >> implementation.
> > > >> > >> > Bit of surfing lead me to
> > > >> > >> > http://www.w3.org/Library/User/Architecture/Events.html,
> which
> > > >> says
> > > >> > >> > "LibWWW is not posix thread safe but it uses a
> 'pseudo-thread'
> > > >> model
> > > >> > >> based
> >
> === message truncated ===
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Take Yahoo! Mail with you! Get it on your mobile phone.
> http://mobile.yahoo.com/maildemo
>
>
>


Mime
View raw message