A perfect example of why you would want to do this is your insert_bug.aspx page. It would be much less obscure and provide for better reuse in other applications if you made that a web service instead.
If you mean "web service" in the formal SOAP sense of the term, that's just one of many ways to do it, and not necessarily the easiest. Out in the real world, it's not even that common.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
With the way you are doing it you need to know the magical parameters to send and recieve for the response/post. With SOAP webservices and primarily WSDL your program automatically knows what the input and output parameters are and everything is strongly typed.
As far as not being used in the real world thats kinda wierd, thats all we ever used when interacting with other companys accross the internet as well as internally in a wide variety of scenarios for our customers when I was still doing consulting. It's a standard, and it's used everywhere. Some very well known examples are the USPS, UPS, and Fedex web services.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I guess our real-world experiences differ.
Note that SOAP is being challenged today by REST. Google SOAP versus REST.
Just about every approach has pros and cons.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you mean "web service" in the formal SOAP sense of the term, that's just one of many ways to do it, and not necessarily the easiest. Out in the real world, it's not even that common.
With the way you are doing it you need to know the magical parameters to send and recieve for the response/post. With SOAP webservices and primarily WSDL your program automatically knows what the input and output parameters are and everything is strongly typed.
As far as not being used in the real world thats kinda wierd, thats all we ever used when interacting with other companys accross the internet as well as internally in a wide variety of scenarios for our customers when I was still doing consulting. It's a standard, and it's used everywhere. Some very well known examples are the USPS, UPS, and Fedex web services.
I guess our real-world experiences differ.
Note that SOAP is being challenged today by REST. Google SOAP versus REST.
Just about every approach has pros and cons.