axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From susan...@apache.org
Subject cvs commit: xml-axis/c/docs TODO.txt
Date Wed, 17 Sep 2003 04:25:21 GMT
susantha    2003/09/16 21:25:21

  Modified:    c/docs   TODO.txt
  Log:
  updated with latest info
  
  Revision  Changes    Path
  1.26      +7 -6      xml-axis/c/docs/TODO.txt
  
  Index: TODO.txt
  ===================================================================
  RCS file: /home/cvs/xml-axis/c/docs/TODO.txt,v
  retrieving revision 1.25
  retrieving revision 1.26
  diff -u -r1.25 -r1.26
  --- TODO.txt	20 Aug 2003 06:26:46 -0000	1.25
  +++ TODO.txt	17 Sep 2003 04:25:21 -0000	1.26
  @@ -42,7 +42,7 @@
   		So we have to make Serializer/Deserializer code to a DLL and then every web service and
the
   		Axis engine uses the same DLL.
   ! <team> 	going through the Axis C++ code and minimize the usage of STL as much as
possible (specially std::string)
  -* <susantha> 	Improving the code in XMLStreamHandler.cpp to avoid XMLString::transcode
  +X <susantha> 	Improving the code in XMLStreamHandler.cpp to avoid XMLString::transcode
   
   DOCUMENTATION
   -------------
  @@ -80,9 +80,10 @@
   -----------------------
   ! <team>	Support for internationalization require you to handle user data with unicodes
so
   		replace std::string with std::wstring & char * with wchar_t* where user data is handled.
  -! <team> 	Refactor AxisEngine to make it suitable for Server side & Client side
seperatly
  -		so that we can derive AxisServer & AxisClient from that and no duplication result
in.
  -! <team>	Clean seperation would be required between XML writing & reading so
that we can easily 
  +X <susantha> 	Refactor AxisEngine to make it suitable for Server side & Client
side seperatly
  +X <sanjaya>	so that we can derive AxisServer & AxisClient from that and no duplication
result in.
  +
  +X <team>	Clean seperation would be required between XML writing & reading so
that we can easily 
   		plug in different XML parsing mechanisms.
   ! <team> 	Better if we can introduce namespaces to avoid collisions between names
when the 
   		server/client side is link with user code. Hence, better to focus it now rather than
later.		
  @@ -110,8 +111,8 @@
   ! <team> 	Pluggable transport API for server & client, seperate interfaces between
Transport & 
   		other stuff.
   ! <team> 	Support for "SOAP messages with attachments"
  -! <team>
  -		Development of following transport modules and testing them
  +
  +* <team>	Development of following transport modules and testing them
   			1. Apache 1.3 for linux
   			2. IIS
   			3. Apache 2.0 for windows and Linux
  
  
  

Mime
View raw message