Unlike traditional client/server models, such as a Web server/Web page system, Web services do not provide the user with a GUI. Web services instead share business logic, data and processes through a programmatic interface across a network. The applications interface, not the users. Developers can then add the Web service to a GUI (such as a Web page or an executable program) to offer specific functionality to users.
When a registrar registers a com domain name for an end-user, it must pay a maximum annual fee of US$7.34 to VeriSign, the registry operator for com, and a US$0.18 annual administration fee to ICANN. Most domain registrars price their services and products to address both the annual fees and the administration fees that must be paid to ICANN. Barriers to entry into the bulk registrar industry are high for new companies without an existing customer base.[citation needed]
In 1993 the U.S. Department of Commerce, in conjunction with several public and private entities, created InterNIC to maintain a central database that contains all the registered domain names and the associated IP addresses in the U.S. (other countries maintain their own NICs (Network Information Centers) -- there's a link below that discusses Canada's system, for example). Network Solutions, a member of InterNIC, was chosen to administer and maintain the growing number of Internet domain names and IP addresses. This central database is copied to Top Level Domain (TLD) servers around the world and creates the primary routing tables used by every computer that connects to the Internet.
Web services architecture: the service provider sends a WSDL file to UDDI. The service requester contacts UDDI to find out who is the provider for the data it needs, and then it contacts the service provider using the SOAP protocol. The service provider validates the service request and sends structured data in an XML file, using the SOAP protocol. This XML file would be validated again by the service requester using an XSD file.

A web service always hides the internal complexity of the service to its clients. For an example, an airliner which is selling tickets via a third party portal is only gathering end user info via a web service and in return it is providing ticket. The portal which is selling ticket doesn't have to bother about the internal complexity of the airlines ticket reservation systems.


* NTT America endeavors to make the domain name availability search process reliable; however, NTT America does not guarantee availability of domain names or the accuracy or security of the WHOIS system. There are several factors that could cause a WHOIS.NET query to incorrectly display that a currently registered domain is available. Regardless, if a domain name is already registered, WHOIS.NET will not be able to register the domain or gain possession of the registration from the current registrar without the permission of the current owner. The registration process is not complete until the domain name requested by you has been registered in your name with the appropriate registry. Because there are delays in the actual registration of a domain name with the appropriate registry, NTT America is not responsible if domain names requested by you are actually registered to third parties. Registration of the domain name through NTT America is not complete until you receive the final confirmation e-mail from NTT America. All registrations through NTT America are subject to NTT America's Global Terms and Conditions.

×