1TODO: 2make sure soap 1.1 and 1.2 is supported fully 3Better WSDL support Client and server (how much validation is needed here?) 4UDDI?? 5make internal references for soap encoding (use serialization logic) 6add ini option for always soap_error_handler 7provide user space overriding of serialization certin objects and types 8serialization in general needs to be polished/finished... all xsd types 9look to see if php-soap will work with out always_populate_raw_post_data on 10see if client will work with ssl.. should be eaiser with php_streams 11work on soap serializer (php serialization) 12-work on a soap-service 'regiestry' and 'proxy' (apache soap style) 13-convert all string mainpulation to use smart_str 14make the 'soap' packet abstract.. maybe incorperate xml-rpc 15make the transport layer abstract.. what other transport layers are needed?... who uses smtp? what about jabber? 16make $soap_object->data = 'text'; maybe invoke a set_*() and/or get_*() method 17when using wsdls and function names are similar find the best match 18 void test(int); 19 void test(string); 20 maybe use the same alogrithim as ext/java. 21investigate further http keep_alive... initial testing proved slower.. maybe php_streams will speed things up.. 22provide schema 1999/2001 support.... 23through memory leak testing 24possible using shared memory for sdl caching... 25api for clearing/checking sdl caching... 26make php-soap work as a standalone server using php_streams and the new socket extension 27http authication 28proxy support 29wsdl generation static and auto (.net style (http://server.com/soapserver.php?WSDL)) using phpdoc parsing engine 30interpo testing... 31BENCHMARKING...... lets prove how fast it is. 32do some more work on website 33 34does this list stop... what exactly have i done? 35im sure im forgetting 20 thousand more things.... 36 37 38 - brad 39
