You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Samisa Abeysinghe <sa...@yahoo.com> on 2004/07/15 13:27:37 UTC
Implementation of SOAPTransport interface using LibWWW for client
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!
Re: Axis Java WSDL jars and WSDL2WS tool
Posted by ni...@opensource.lk.
Hi,
I tried to sync WSDL2WS tool with Latest Axis Java Jar due to the impact
of it, I replaced the SchemaUtils.java from Axis java and added some of
the axis c++ functionalty already exisited in SchemaUtils.java,
further some changes to ElementDecl.java and WSDL2Ws.java was also required.
After these changes, WSDL2Ws tool is generating skeletons & wrappers for
server side and stubs for client side as well.
I have attached the files.
rgds,
Nithya
> The current WSDL2WS implementation is based on Axis Java 1.1 Jars.
> Is there any effort to sync the WSDL2WS tool with Latest Axis Java Jars?
>
> Samisa...
>
>
>
> __________________________________
> Do you Yahoo!?
> Vote for the stars of Yahoo!'s next ad campaign!
> http://advision.webevents.yahoo.com/yahoo/votelifeengine/
>
>
>
Axis Java WSDL jars and WSDL2WS tool
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
The current WSDL2WS implementation is based on Axis Java 1.1 Jars.
Is there any effort to sync the WSDL2WS tool with Latest Axis Java Jars?
Samisa...
__________________________________
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
I too agree that we could forget about continue.
However, thread safety is a headache with LibWWW on client side. I would like the client transport
to be thread safe.
Samisa...
--- Sanjiva Weerawarana <sa...@opensource.lk> wrote:
> I understand the principle, but is that a real feature in today's
> Internet? For Web browsing it *may* make sense to have the *HTTP*
> headers checked before the payload is sent (esp. if you have a
> low bandwidth connection like I do), but even that is questionable
> when payload for POSTs in HTTP is almost always very small.
>
> For SOAP stuff, IMO it makes no sense. Why? Because most of the
> time SOAP stuff will be unprocessable by the server because there's
> something wrong in the *SOAP envelope* and not because there's anything
> screwy with the HTTP headers. While whacky clients may use this HTTP
> feature, in practice I don't see it being of any value in the SOAP
> world.
>
> I guess we should still support it because it could be an interop
> problem, but if its too much of a pain I'd say let's not worry too
> hard about it.
>
> Keep-alive and chunking, OTOH, is very real and very useful to have.
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Samisa Abeysinghe" <sa...@yahoo.com>
> To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
> Sent: Monday, July 19, 2004 11:51 AM
> Subject: Re: Implementation of SOAPTransport interface using LibWWW for
> client
>
>
> > Using "Expect: 100-continue" header, your application safes time and
> network (see RFC2616, section
> > 8.2.3).
> >
> > Samisa...
> >
> > --- damitha kumarage <da...@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/
> >
> >
>
>
__________________________________
Do you Yahoo!?
Vote for the stars of Yahoo!'s next ad campaign!
http://advision.webevents.yahoo.com/yahoo/votelifeengine/
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
I understand the principle, but is that a real feature in today's
Internet? For Web browsing it *may* make sense to have the *HTTP*
headers checked before the payload is sent (esp. if you have a
low bandwidth connection like I do), but even that is questionable
when payload for POSTs in HTTP is almost always very small.
For SOAP stuff, IMO it makes no sense. Why? Because most of the
time SOAP stuff will be unprocessable by the server because there's
something wrong in the *SOAP envelope* and not because there's anything
screwy with the HTTP headers. While whacky clients may use this HTTP
feature, in practice I don't see it being of any value in the SOAP
world.
I guess we should still support it because it could be an interop
problem, but if its too much of a pain I'd say let's not worry too
hard about it.
Keep-alive and chunking, OTOH, is very real and very useful to have.
Sanjiva.
----- Original Message -----
From: "Samisa Abeysinghe" <sa...@yahoo.com>
To: "Apache AXIS C Developers List" <ax...@ws.apache.org>
Sent: Monday, July 19, 2004 11:51 AM
Subject: Re: Implementation of SOAPTransport interface using LibWWW for
client
> Using "Expect: 100-continue" header, your application safes time and
network (see RFC2616, section
> 8.2.3).
>
> Samisa...
>
> --- damitha kumarage <da...@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/
>
>
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Using "Expect: 100-continue" header, your application safes time and network (see RFC2616, section
8.2.3).
Samisa...
--- damitha kumarage <da...@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/
Re: Implementation of SOAPTransport interface using LibWWW for
client
Posted by damitha kumarage <da...@opensource.lk>.
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!
Re: Client failed to load parser lib - axiscpp.conf location changed
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi Damitha,
I hardly use deploy_apache2.sh (or deploy_apache.sh) as I less often use the server side.
I usually only use the client side (as per my requirement), and often with my own custom
settings.
However, this kind of a change (like introducing a new folder) should have been informed over
the mailing list, as there can be many who do not use the default settings like me. It is ok to
use 'etc' but only if I new, it could have saved my time.
Thanks for the reply.
Regards,
Samisa...
--- damitha kumarage <da...@opensource.lk> wrote:
> Hi Samisa,
> When installing axiscpp.conf is copied into $AXISCPP_DEPLOY/etc
> by the installer. And this place is correctly located by the engine
> by use of $AXISCPP_DEPLOY env.
> So there is nothing to do manually to locate axiscpp.conf.
> You may be copying the files in the older way.
> Anyway when you run $AXISCPP_DEPLOY/bin/deploy_apache2.sh if it can't
> find axiscpp.conf it complains like this
>
> cannot stat `../etc/axiscpp.conf_linux': No such file or directory
>
> thanks
> damitha
>
> On Mon, 2004-08-02 at 09:59, Samisa Abeysinghe wrote:
> > I spent several hours struglling to get the client working as it was complaining
> > "Exception : DLOPEN FAILED in loading parser library"
> >
> > I checked and rechecked the settings on my systems several times but they were correct.
> >
> > Looking into the code, I found that the location of axiscpp.conf has been changed from
> > $AXISCPP_DEPLOY/axiscpp.conf to $AXISCPP_DEPLOY/etc/axiscpp.conf
> >
> > I am not sure if this change was informed to the mailing list (to my knowlege, I did not see
> any
> > message).
> > However, if you get problems running the client, please check this.
> >
> > Thanks,
> > Samisa...
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Address AutoComplete - You start. We finish.
> > http://promotions.yahoo.com/new_mail
> >
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - Helps protect you from nasty viruses.
http://promotions.yahoo.com/new_mail
Re: Client failed to load parser lib - axiscpp.conf location
changed
Posted by damitha kumarage <da...@opensource.lk>.
Hi Samisa,
When installing axiscpp.conf is copied into $AXISCPP_DEPLOY/etc
by the installer. And this place is correctly located by the engine
by use of $AXISCPP_DEPLOY env.
So there is nothing to do manually to locate axiscpp.conf.
You may be copying the files in the older way.
Anyway when you run $AXISCPP_DEPLOY/bin/deploy_apache2.sh if it can't
find axiscpp.conf it complains like this
cannot stat `../etc/axiscpp.conf_linux': No such file or directory
thanks
damitha
On Mon, 2004-08-02 at 09:59, Samisa Abeysinghe wrote:
> I spent several hours struglling to get the client working as it was complaining
> "Exception : DLOPEN FAILED in loading parser library"
>
> I checked and rechecked the settings on my systems several times but they were correct.
>
> Looking into the code, I found that the location of axiscpp.conf has been changed from
> $AXISCPP_DEPLOY/axiscpp.conf to $AXISCPP_DEPLOY/etc/axiscpp.conf
>
> I am not sure if this change was informed to the mailing list (to my knowlege, I did not see any
> message).
> However, if you get problems running the client, please check this.
>
> Thanks,
> Samisa...
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail Address AutoComplete - You start. We finish.
> http://promotions.yahoo.com/new_mail
>
Re: Client crashes with both transports
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
OK, I found the solution:
SoapSerializer::releaseBufferCallBack has been removed from the serializer.
Hence it makes no sence to use m_pReleaseBufferCallback anymore.
(Yes I remeber that I saw a email thread on removal of buffering: Cool)
Now I have a question, who should (or does) delete the passed pointer to sendBytes?
Also, would it be not nice to update all the codes when applying a patch? (Or at lease use
depricate option in place; please)
PS: I did not touch the serializer code to fix this rather only the LibWWW trasport code.
I cannot still get the other trasport (axis transport i.e.) working.
Thanks,
Samisa...
--- Samisa Abeysinghe <sa...@yahoo.com> wrote:
> I have been working on the LibWWW trasport to ensure thread safety.
>
> I was able to get my updates working with the cvs checkout I got on 27th.
> However, when I tried the same with the latest cvs this morning, I saw the client was crashing.
>
> The point of crash is
> 0x40153185 in LibWWWTransport::sendBytes(char const*, void const*) (this=0x8059be8,
> pcSendBuffer=0x4007a0e0 "<?xml version='1.0' encoding='utf-8' ?>", pBufferid=0x8059b98) at
> LibWWWTransport.cpp:133
>
> where it calls:
> m_pReleaseBufferCallback(pcSendBuffer, pBufferid);
>
> I tested the client with Axis trasport as well, that too fails to work.
>
> I doubt the latest changes to SoapSerializer class would have caused the problems.
> I am desperate to finish off the LibWWW related work. But this bug is a bloker.
> Please help fix this.
>
> Thanks,
> Samisa...
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
Client crashes with both transports
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
I have been working on the LibWWW trasport to ensure thread safety.
I was able to get my updates working with the cvs checkout I got on 27th.
However, when I tried the same with the latest cvs this morning, I saw the client was crashing.
The point of crash is
0x40153185 in LibWWWTransport::sendBytes(char const*, void const*) (this=0x8059be8,
pcSendBuffer=0x4007a0e0 "<?xml version='1.0' encoding='utf-8' ?>", pBufferid=0x8059b98) at
LibWWWTransport.cpp:133
where it calls:
m_pReleaseBufferCallback(pcSendBuffer, pBufferid);
I tested the client with Axis trasport as well, that too fails to work.
I doubt the latest changes to SoapSerializer class would have caused the problems.
I am desperate to finish off the LibWWW related work. But this bug is a bloker.
Please help fix this.
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
Client failed to load parser lib - axiscpp.conf location changed
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
I spent several hours struglling to get the client working as it was complaining
"Exception : DLOPEN FAILED in loading parser library"
I checked and rechecked the settings on my systems several times but they were correct.
Looking into the code, I found that the location of axiscpp.conf has been changed from
$AXISCPP_DEPLOY/axiscpp.conf to $AXISCPP_DEPLOY/etc/axiscpp.conf
I am not sure if this change was informed to the mailing list (to my knowlege, I did not see any
message).
However, if you get problems running the client, please check this.
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
Yahoo! Mail Address AutoComplete - You start. We finish.
http://promotions.yahoo.com/new_mail
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1 for using -I and -L properly ..
Sanjiva.
----- Original Message -----
From: "John Hawkins" <HA...@uk.ibm.com>
To: "Apache AXIS C Developers List" <ax...@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 <ax...@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 <HA...@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 <ax...@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 <da...@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
>
>
>
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by John Hawkins <HA...@uk.ibm.com>.
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 <ax...@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 <HA...@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 <ax...@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 <da...@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
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
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 <HA...@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 <ax...@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 <da...@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
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by John Hawkins <HA...@uk.ibm.com>.
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 <ax...@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 <da...@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
> >> > >> > 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!?
> >> > > Yahoo! Mail is new and improved - Check it out!
> >> > > http://promotions.yahoo.com/new_mail
> >> > >
> >> > >
> >>
> >>
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > New and Improved Yahoo! Mail - 100MB free storage!
> > http://promotions.yahoo.com/new_mail
> >
> >
Re: Implementation of SOAPTransport interface using LibWWW for
client
Posted by damitha kumarage <da...@opensource.lk>.
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 <da...@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
> >> > >> > 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!?
> >> > > Yahoo! Mail is new and improved - Check it out!
> >> > > http://promotions.yahoo.com/new_mail
> >> > >
> >> > >
> >>
> >>
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > New and Improved Yahoo! Mail - 100MB free storage!
> > http://promotions.yahoo.com/new_mail
> >
> >
Re: Implementation of SOAPTransport interface using LibWWW for
client
Posted by la...@opensource.lk.
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 <da...@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
>> > >> > 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!?
>> > > Yahoo! Mail is new and improved - Check it out!
>> > > http://promotions.yahoo.com/new_mail
>> > >
>> > >
>>
>>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
>
>
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
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 <da...@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
> > >> > 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!?
> > > Yahoo! Mail is new and improved - Check it out!
> > > http://promotions.yahoo.com/new_mail
> > >
> > >
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
Re: Implementation of SOAPTransport interface using LibWWW for
client
Posted by damitha kumarage <da...@opensource.lk>.
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
> >> > 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!?
> > Yahoo! Mail is new and improved - Check it out!
> > http://promotions.yahoo.com/new_mail
> >
> >
Re: Implementation of SOAPTransport interface using LibWWW for
client
Posted by la...@opensource.lk.
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
>> > 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!?
> Yahoo! Mail is new and improved - Check it out!
> http://promotions.yahoo.com/new_mail
>
>
Re: [Threads] Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
--- John Hawkins <HA...@uk.ibm.com> wrote:
>
>
>
>
> Hi Samisa,
>
> So, just to confirm what you are saying:
>
> A user creates a Stub, they can set up that stub then call the service.
> After that they have to throw away that stub and then recreate another one
> to call the next method on the service (or even the same method)?
>
Yes, John. This sounds correct. When I have multiple threads. I cannot reuse a stub object to call
another method (due to the initilizations done for each and every method)
> Have you tested the scenario of having to create another instance of the
> stub in the same process?
Yes in the same thread, more than one stub could exist.
(This was made possible by a hack that I applied make sure some of the one off inits at lib
level.)
However, dispatching multiple requests on the same stub still remains problamatic.
Thanks,
Samisa...
>
> Thanks for all your efforts with libwww - you obviously know it inside out
> now :-)
>
>
>
> John Hawkins
>
>
>
>
>
> Samisa Abeysinghe
> <samisa_abeysingh
> e@yahoo.com> To
> Apache AXIS C Developers List
> 09/08/2004 07:46 <ax...@ws.apache.org>
> cc
>
> Please respond to Subject
> "Apache AXIS C Re: [Threads] Implementation of
> Developers List" SOAPTransport interface using
> LibWWW for client
>
>
>
>
>
>
>
>
>
>
> Hi All,
> I have been spending so much time (in fact too much ;-)) on getting
> LibWWW transport to be
> thread safe.
>
> I have managed to get the threaded client working with LibWWW with
> restrictions.
> The restriction is that a thread could dispatch only one method call
> per stub. If you try to
> dispatch two or more then the client fails.
> The problem could be fixed. But with the current desing of the way in
> which the stub handles
> the trasport prohibits this. One main problem is that the Stub creates a
> new trasport object for
> each method invocation. This prevents me doing some one off lib level
> initializations of trasport
> (this is a must in LibWWW). This could be solved by having thread specific
> logic (e.g. use of
> locking) in the trasport code itself. However, I do not think this is the
> correct way to do it
> because then we have to have thread specific code in the trasport.
> The problems are mainly due to the fact that the level of control that
> we can have on the way
> we control trasport from the Stub. This is acceptable with AxisTransport,
> which is the original
> transport of Axis C++. However, if we are to use LibWWW in a thread safe
> manner, there need to be
> some drastic design cnages to the interaction between
> Serializer/Deserializer and the trasport.
> (Basically state management has to be re-thought) I hope these will be
> taken up with the proposed
> refactoring/new-design of Axis C++.
> For the time being, we have to live with LibWWW trasport not being
> truely thread safe.
> Thanks,
> Samisa...
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail is new and improved - Check it out!
> http://promotions.yahoo.com/new_mail
>
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
Re: [Threads] Implementation of SOAPTransport interface using LibWWW for
client
Posted by John Hawkins <HA...@uk.ibm.com>.
Hi Samisa,
So, just to confirm what you are saying:
A user creates a Stub, they can set up that stub then call the service.
After that they have to throw away that stub and then recreate another one
to call the next method on the service (or even the same method)?
Have you tested the scenario of having to create another instance of the
stub in the same process?
Thanks for all your efforts with libwww - you obviously know it inside out
now :-)
John Hawkins
Samisa Abeysinghe
<samisa_abeysingh
e@yahoo.com> To
Apache AXIS C Developers List
09/08/2004 07:46 <ax...@ws.apache.org>
cc
Please respond to Subject
"Apache AXIS C Re: [Threads] Implementation of
Developers List" SOAPTransport interface using
LibWWW for client
Hi All,
I have been spending so much time (in fact too much ;-)) on getting
LibWWW transport to be
thread safe.
I have managed to get the threaded client working with LibWWW with
restrictions.
The restriction is that a thread could dispatch only one method call
per stub. If you try to
dispatch two or more then the client fails.
The problem could be fixed. But with the current desing of the way in
which the stub handles
the trasport prohibits this. One main problem is that the Stub creates a
new trasport object for
each method invocation. This prevents me doing some one off lib level
initializations of trasport
(this is a must in LibWWW). This could be solved by having thread specific
logic (e.g. use of
locking) in the trasport code itself. However, I do not think this is the
correct way to do it
because then we have to have thread specific code in the trasport.
The problems are mainly due to the fact that the level of control that
we can have on the way
we control trasport from the Stub. This is acceptable with AxisTransport,
which is the original
transport of Axis C++. However, if we are to use LibWWW in a thread safe
manner, there need to be
some drastic design cnages to the interaction between
Serializer/Deserializer and the trasport.
(Basically state management has to be re-thought) I hope these will be
taken up with the proposed
refactoring/new-design of Axis C++.
For the time being, we have to live with LibWWW trasport not being
truely thread safe.
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
Re: [Threads] Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi All,
I have been spending so much time (in fact too much ;-)) on getting LibWWW transport to be
thread safe.
I have managed to get the threaded client working with LibWWW with restrictions.
The restriction is that a thread could dispatch only one method call per stub. If you try to
dispatch two or more then the client fails.
The problem could be fixed. But with the current desing of the way in which the stub handles
the trasport prohibits this. One main problem is that the Stub creates a new trasport object for
each method invocation. This prevents me doing some one off lib level initializations of trasport
(this is a must in LibWWW). This could be solved by having thread specific logic (e.g. use of
locking) in the trasport code itself. However, I do not think this is the correct way to do it
because then we have to have thread specific code in the trasport.
The problems are mainly due to the fact that the level of control that we can have on the way
we control trasport from the Stub. This is acceptable with AxisTransport, which is the original
transport of Axis C++. However, if we are to use LibWWW in a thread safe manner, there need to be
some drastic design cnages to the interaction between Serializer/Deserializer and the trasport.
(Basically state management has to be re-thought) I hope these will be taken up with the proposed
refactoring/new-design of Axis C++.
For the time being, we have to live with LibWWW trasport not being truely thread safe.
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
Re: Implementation of SOAPTransport interface using LibWWW for
client
Posted by la...@opensource.lk.
Hi Samisa,
There is a compiler error when compiling Libwww transport library on
windows. The error massage is as follows.
C:\test\ws-axis\c\src\transport\libwww\LibWWWTransport.cpp(423) : error
C2065: 'METHOD_EXT_0' : undeclared identifier
Lahiru Wimalasiri
> Well Bad news :-(
>
> Threads are failing again on Linux with LibWWW.
> I had mistakenly tested with a join in the test program.
>
> However, with the same logic, a standalone program works with Axis Java.
> Things go wrong when I
> integrate with Axis C++.
>
> Samisa...
>
> --- John Hawkins <HA...@uk.ibm.com> wrote:
>
>>
>>
>>
>>
>> Excellent work Samisa !
>>
>> John Hawkins
>>
>>
>>
>>
>>
>> Samisa Abeysinghe
>> <samisa_abeysingh
>> e@yahoo.com>
>> To
>> Apache AXIS C Developers List
>> 02/08/2004 08:06 <ax...@ws.apache.org>
>> cc
>>
>> Please respond to
>> Subject
>> "Apache AXIS C Re: Implementation of
>> SOAPTransport
>> Developers List" interface using LibWWW for
>> client
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Hi All,
>> I have been fortunate enough to get the threads working with LibWWW.
>>
>> I have tested this on Linux and did not find any problems.
>>
>> I have included some documentation in
>> docs/LibWWW-transport-HOWTO.txt.
>> (threds, 100-continue,
>> use of Expat etc.)
>> The same is avaialble at src/transport/libwww/readme.txt
>>
>> Lahiru has included some info on how to use this transport on
>> Windows.
>> If possible please test the latest on Windows. (it is worth testing
>> thread safety on windows as
>> well)
>> Thanks,
>> Samisa...
>>
>>
>>
>> __________________________________
>> Do you Yahoo!?
>> Yahoo! Mail - 50x more storage than other providers!
>> http://promotions.yahoo.com/new_mail
>>
>>
>>
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> New and Improved Yahoo! Mail - 100MB free storage!
> http://promotions.yahoo.com/new_mail
>
>
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Well Bad news :-(
Threads are failing again on Linux with LibWWW.
I had mistakenly tested with a join in the test program.
However, with the same logic, a standalone program works with Axis Java. Things go wrong when I
integrate with Axis C++.
Samisa...
--- John Hawkins <HA...@uk.ibm.com> wrote:
>
>
>
>
> Excellent work Samisa !
>
> John Hawkins
>
>
>
>
>
> Samisa Abeysinghe
> <samisa_abeysingh
> e@yahoo.com> To
> Apache AXIS C Developers List
> 02/08/2004 08:06 <ax...@ws.apache.org>
> cc
>
> Please respond to Subject
> "Apache AXIS C Re: Implementation of SOAPTransport
> Developers List" interface using LibWWW for
> client
>
>
>
>
>
>
>
>
>
>
> Hi All,
> I have been fortunate enough to get the threads working with LibWWW.
>
> I have tested this on Linux and did not find any problems.
>
> I have included some documentation in docs/LibWWW-transport-HOWTO.txt.
> (threds, 100-continue,
> use of Expat etc.)
> The same is avaialble at src/transport/libwww/readme.txt
>
> Lahiru has included some info on how to use this transport on Windows.
> If possible please test the latest on Windows. (it is worth testing
> thread safety on windows as
> well)
> Thanks,
> Samisa...
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Mail - 50x more storage than other providers!
> http://promotions.yahoo.com/new_mail
>
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by John Hawkins <HA...@uk.ibm.com>.
Excellent work Samisa !
John Hawkins
Samisa Abeysinghe
<samisa_abeysingh
e@yahoo.com> To
Apache AXIS C Developers List
02/08/2004 08:06 <ax...@ws.apache.org>
cc
Please respond to Subject
"Apache AXIS C Re: Implementation of SOAPTransport
Developers List" interface using LibWWW for
client
Hi All,
I have been fortunate enough to get the threads working with LibWWW.
I have tested this on Linux and did not find any problems.
I have included some documentation in docs/LibWWW-transport-HOWTO.txt.
(threds, 100-continue,
use of Expat etc.)
The same is avaialble at src/transport/libwww/readme.txt
Lahiru has included some info on how to use this transport on Windows.
If possible please test the latest on Windows. (it is worth testing
thread safety on windows as
well)
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
Hi All,
I have been fortunate enough to get the threads working with LibWWW.
I have tested this on Linux and did not find any problems.
I have included some documentation in docs/LibWWW-transport-HOWTO.txt. (threds, 100-continue,
use of Expat etc.)
The same is avaialble at src/transport/libwww/readme.txt
Lahiru has included some info on how to use this transport on Windows.
If possible please test the latest on Windows. (it is worth testing thread safety on windows as
well)
Thanks,
Samisa...
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
Re: Implementation of SOAPTransport interface using LibWWW for client
Posted by Samisa Abeysinghe <sa...@yahoo.com>.
--- 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
> > 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!?
Yahoo! Mail is new and improved - Check it out!
http://promotions.yahoo.com/new_mail
Re: Implementation of SOAPTransport interface using LibWWW for
client
Posted by la...@opensource.lk.
Hi All,
I have tested it on windows. all the samples are working on windows. But
it seems considerably slow.
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
> 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!
RE: Implementation of SOAPTransport interface using LibWWW for client
Posted by Susantha Kumara <su...@opensource.lk>.
Great job Samisa.
What is this 100-continue ?
Susantha
---
-----Original Message-----
From: Samisa Abeysinghe [mailto:samisa_abeysinghe@yahoo.com]
Sent: Thursday, July 15, 2004 5:28 PM
To: Apache AXIS C Developers List
Subject: Implementation of SOAPTransport interface using LibWWW for
client
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
<http://us.rd.yahoo.com/mail_us/taglines/new/*http:/promotions.yahoo.com
/new_mail> it out!