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:51:52 UTC
cvs commit: ws-axis/c/src/transport/libwww readme.txt
samisa 2004/09/05 23:51:52
Modified: c/src/transport/libwww readme.txt
Log:
Updated the thread safety related information
Revision Changes Path
1.6 +6 -4 ws-axis/c/src/transport/libwww/readme.txt
Index: readme.txt
===================================================================
RCS file: /home/cvs/ws-axis/c/src/transport/libwww/readme.txt,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- readme.txt 2 Aug 2004 06:05:30 -0000 1.5
+++ readme.txt 6 Sep 2004 06:51:52 -0000 1.6
@@ -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...