>Finally, there is stronger data typing in web services than you will >find in a form-posting solution. On a form post, your ID field (a >numeric) can be sent as "123abc" and you have no control over it. You >have to double-check on the server-side. On a web service, that field >would be guaranteed to be numeric. Checking is done on the client >(consumer) side without having to hit your back-end server.
That's not 100% accurate - at least the part about it being done on the client side. You can build up your own SOAP envelope (example here: http://jibbering.com/2002/4/httprequest.html - scroll down to "Using XMLHTTP with GOOGLE's SOAP API") and put a string in a field marked as "int". What you gain by using SOAP (in cf at least) is that the server side checking is done by the framework, so you don't have to write any of it. Better yet, if you do submit such a malformed SOAP request you get a nice standardized error response. If you have one parameter then you're not gaining much, but if you have dozens ... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:214424 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
