advertisement

Weblog:   Web Services, Weblogs and the Future.
Subject:   Use SOAP
Date:   2003-05-28 18:38:31
From:   anonymous2
Response to: Use SOAP

Agreed on SOAP. Simple it Ain't.


On HTTP, you have to handle types (is is a date? Is it an integer? Is it a string?) on the server, and you'd have to know what it is, because 06116 is a zip code, a string, not an integer, so for every item of data, you'd have to send the type too, as in Val=06116&Type=String. But what if you're sending 3 values in a row? Which type applies to which value? or do you number them? as:


val1=06116&type1=string&val2=04&type2=integer&val3=Connecticut&type3=string


for:
ZipCode 06116
StateCode 04
StateName Connecticut


Then you end up with a parsing nightmare, with arrays, and how large are the arrays... So on and so forth.


Trust me, for structs, it would not be pretty.
Full Threads Newest First

Showing messages 1 through 2 of 2.

  • Data in the XML not the URL
    2003-06-19 18:26:32  anonymous2 [Reply | View]

    If the server doesn't know how to deal with the untyped data in a URL, having clients send that extra data won't help - how will it know that the client is /wrong/?

    If you need strong typing, put it in the body of the request message, not the resource identifier.

    The resource identifier (URI) isn't (shouldn't be) different if the zipcode is identified as an integer .vs. text.
  • Data in the XML not the URL
    2003-06-19 18:29:32  anonymous2 [Reply | View]

    If the server doesn't know how to deal with the untyped data in a URL, having clients send that extra data won't help - how will it know that the client is /wrong/?

    If you need strong typing, put it in the body of the request message, not the resource identifier.

    The resource identifier (URI) isn't (shouldn't be) different if the zipcode is identified as an integer .vs. text.
Showing messages 1 through 2 of 2.