Some people in the community are asking the basic issues of WebServices:
What is the use of webservicse?
Here is my reply:
This is a good problem, all of the people who begin to learn Webservices should ask such a problem. Similar questions, why do you want to use WebServices, not similar services, like transoting, or java?
The reason why it is true that many people don't even understand this basic problem, starting the pile of CODE, smashing, and entering the death.
A pile of nonsense, talk about my own opinion, is a throwing brick:
What can WebServices do other (formerly) technology can't be or difficult?
Two most important things:
1, good connection,
99% of WebServices use HTTP protocol to implement transmission, while the 80-port used by the standard HTTP protocol is almost open in all firewalls. In other words, if your machine can access the website, we can use WebServices. There is no technique that has not been said before, because they mostly use the proprietary protocol (port). In the internal network, these protocols are different, but the firewall has different inside and outside.
Corba, DCOM, RMI, these stuff have some years, but no one can be said to be very popular, one of the problems is not difficult, but the application field is very limited. The supplier said that their system supports Cobra, so that we can get an instant offer and spot inventory, but our even the client software they offer is not used, unless they can open the Internet on the firewall.
2, chicken with duck
Hong Kong movies often see this phrase, if we let Java's JMS and .NET Remoting speak, it is basically this. It seems that it seems to be so, actually a cattle head to the horse mouth. This should be an additional connection performance. In fact, let RMI and transing dialogue may be difficult than the chicken with duck.
But WebServices can really let chickens with ducks, not only, almost any language is communicating, because he asks you to use a Chinese language (SOAP). Any technique (we) that can communicate with this language now can now join the WebServices of the family. Here, there is a common web description language (PEEL, PHP, JSP, ASP, etc.), common universal languages (C / C , Pascal, Basic, Java, C #, etc.), as long as you can make XML packages in the SOAP format You can communicate with other WebServices vendors. So, you don't have to use any language tools, you can get a SOAP package, or you can get a response. XML belongs to the non-wear self-description language, even for hundreds of years, you can also understand the contents of the complex tool.
Can refer to my previous thing:
Basic concept of Web Services
In China, unlike ASP.NET already wind, WebServices is still in its infancy, I really hope that the community WebServices administrators can tell these basic things.
