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 refrences for soap encoding (use seralization 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 9make perstistant objects and work with or without register_globals on 10look to see if php-soap will work with out always_populate_raw_post_data on 11see if client will work with ssl.. should be eaiser with php_streams 12work on soap seralizer (php serialization) 13-work on a soap-service 'regiestry' and 'proxy' (apache soap style) 14-convert all string mainpulation to use smart_str 15make the 'soap' packet abstract.. maybe incorperate xml-rpc 16make the transport layer abstract.. what other transport layers are needed?... who uses smtp? what about jabber? 17make $soap_object->data = 'text'; maybe invoke a set_*() and/or get_*() method 18when using wsdls and function names are similar find the best match 19 void test(int); 20 void test(string); 21 maybe use the same alogrithim as ext/java. 22investigate further http keep_alive... inital testing proved slower.. maybe php_streams will speed things up.. 23provide schema 1999/2001 support.... 24through memory leak testing 25possible using shared memory for sdl caching... 26api for clearing/checking sdl caching... 27make php-soap work as a standalone server using php_streams and the new socket extension 28http authication 29proxy support 30wsdl generation static and auto (.net style (http://server.com/soapserver.php?WSDL)) using phpdoc parsing engine 31interpo testing... 32BENCHMARKING...... lets prove how fast it is. 33do some more work on website 34 35does this list stop... what exactly have i done? 36im sure im forgetting 20 thousand more things.... 37 38 39 - brad 40
