154Re: [soap-newbies] New Message: Comments on WSDL
- Nov 5, 2001In article <0c3c01c1662a$b00d0f30$33a1dc40@murphy>, Dave Winer
>The problem is this -- in a dynamic environment, I can't automaticallyIsn't this back to front? It's the programmer producing the server that
>generate WSDL because while I may know the number of incoming params, I have
>no idea what their type is. Only the programmer knows.
needs to generate the WSDL and presumably they know what types the
And as for the reader of the WSDL, writing the client, they already know
how to convert the SOAP types to their local internal types.
If this is an argument about strong typing, last time I looked both SOAP
and XML-RPC were inherently string typed, and weakly typed environments
like PHP already have to jump through hoops to cope with them. Adding an
additional translation layer to dynamically connect to a server via WSDL
looks hard but not impossible. The issue of typing is no different from
what we're already having to cope with.
This also ignores the end-point definitions in WSDL. Once you've built
the client that connects to a specific server, WSDL could provide a
mechanism to redirect to a new instance of the server without any other
In article <9s6r0h+9bd@...>, tblanchard2@... writes
>From: "Doug Davis" <dug@u...>LOL! And even more so with XML-RPC, but that's another story ;-)
>Incidentally - in your first rant - I could replace the phrase WSDL
>with SOAP and add Userland to the list of company names and you'd
>pretty well capture how I feel about SOAP.
Julian Bond email: julian_bond@...
M: +44 (0)77 5907 2173 T: +44 (0)192 0412 433
ICQ:33679568 tag:So many words, so little time
- << Previous post in topic Next post in topic >>