You are viewing a plain text version of this content. The canonical link for it is here.
Posted to axis-cvs@ws.apache.org by sa...@apache.org on 2004/09/06 08:48:54 UTC
cvs commit: ws-axis/c/docs LibWWW-transport-HOWTO.txt
samisa 2004/09/05 23:48:54
Modified: c/docs LibWWW-transport-HOWTO.txt
Log:
Updated the thread safety section.
Revision Changes Path
1.2 +6 -4 ws-axis/c/docs/LibWWW-transport-HOWTO.txt
Index: LibWWW-transport-HOWTO.txt
===================================================================
RCS file: /home/cvs/ws-axis/c/docs/LibWWW-transport-HOWTO.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- LibWWW-transport-HOWTO.txt 2 Aug 2004 06:15:07 -0000 1.1
+++ LibWWW-transport-HOWTO.txt 6 Sep 2004 06:48:54 -0000 1.2
@@ -98,10 +98,12 @@
http://www.w3.org/Library/User/Architecture/Events.html says
“LibWWW is not posix thread safe but it uses a 'pseudo-thread'
model based on non-blocking sockets and interleaved IO.”
-I did a bit of research and figured out how to make this implementation
-thread safe. I was able to successfully use the 'pseudo-thread'
-model of LibWWW and achieve thread safety. You could test the thread
-safety with the test in tests/client/threadSafe/.
+I did a bit of research and figured out how to make LibWWW thread safe.
+However I was unable to successfully use the 'pseudo-thread'
+model of LibWWW and achieve thread safety with Axis C++. I think the problem
+could be solved by enabling library level one off initilizations possible
+from a globle initilizer, which is not supported by current Axis C++
+architecture. Hence thread safety with LibWWW remains a TODO.
- Samisa...