axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samisa Abeysinghe <samisa_abeysin...@yahoo.com>
Subject Re: Implementation of SOAPTransport interface using LibWWW for client
Date Mon, 19 Jul 2004 05:51:04 GMT
Using "Expect: 100-continue" header, your application safes time and network (see RFC2616,
section
8.2.3).

Samisa...

--- damitha kumarage <damitha@opensource.lk> wrote:
> Well done Samisa,
> What is this 100-continue?
> 
> damitha
> On Thu, 2004-07-15 at 17:27, Samisa Abeysinghe wrote:
> > 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 on non-blocking sockets and interleaved IO." Bit of research is
> > needed to figure out how to make this implementation thread safe. It
> > remains a TODO as of now.
> > 
> > Thanks,
> > 
> > Samisa...
> > 
> > 
> > ______________________________________________________________________
> > Do you Yahoo!?
> > Yahoo! Mail is new and improved - Check it out!
> 
> 



		
__________________________________
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/


Mime
View raw message