Re: [AOLSERVER] how to parse Content-Type text/xml form post

2010-04-07 Thread Gustaf Neumann
Grab the post data and use an xml parser to get the content There are multiple xml parsers for tcl available that you can use. I would recommend tdom, which supports among other things xpath (see http://www.tdom.org/) -gustaf neumann Am 07.04.10 06:40, schrieb Brad Chick: This should be fairly

Re: [AOLSERVER] how to parse Content-Type text/xml form post

2010-04-07 Thread Gustaf Neumann
Is there something wrong with ns_conn content ? Am 07.04.10 09:03, schrieb Bas Scheffers: I think the question is *how* to grab the raw post data? On Wednesday, April 7, 2010 4:12pm, Gustaf Neumannneum...@wu-wien.ac.at said: Grab the post data and use an xml parser to get the content

Re: [AOLSERVER] how to parse Content-Type text/xml form post

2010-04-07 Thread Brad Chick
Thanks. That was simple enough. Just a ns_conn content and then tdom. It just wasn't easy to find much info on this. On 4/7/2010 4:31 AM, Gustaf Neumann wrote: Is there something wrong with ns_conn content ? Am 07.04.10 09:03, schrieb Bas Scheffers: I think the question is *how* to grab the

Re: [AOLSERVER] how to parse Content-Type text/xml form post

2010-04-07 Thread Bas Scheffers
Yes, there is something wrong with that: It's not in the documentation! :( Not in the old-style docs anyway and the new Wiki is not responding, just hangs. Again :( Bas. On 07/04/2010, at 6:01 PM, Gustaf Neumann wrote: Is there something wrong with ns_conn content ? Am 07.04.10 09:03,

Re: [AOLSERVER] how to parse Content-Type text/xml form post

2010-04-07 Thread Tom Jackson
Here's an example of an adapter which allows you to develop your xml code independently of your AOLserver code: proc ::wsdl::server::accept { why } { log Notice Accepting Connection with $why foreach {server service port binding address} $why {} # 0. Get POSTed Data: set