Dynamic Discovery of Web Proxy Services
Original Publication Date: 2002-Jun-09
Included in the Prior Art Database: 2003-Jun-21
The present invention describes a method for automatic configuration of Web Proxy services by storing auto-configuration information in a public Universal Discovery, Description, and Integration (UDDI) registry and allowing client applications (such as browsers) to dynamically discover the location of a proxy server by querying the registry for services that provide proxy auto-config information and then programmatically invoking said service without user intervention. The advantages of this approach include multiple implementation alternatives and the fact that user intervention is not required at any time Systems Administrators may update the information in the UDDI registry at any time without requiring that client applications be reconfigured. A UDDI registry maintains information about businesses (businessEntity), the services they offer (businessService), and the interface(s) required to access a service (bindingTemplate). Each service conforms to a given specification (or version of a specification) which is described by a technical model (tModel). A service whose function is to provide information on which proxy server(s) are available, is registered with a UDDI registry. The bindingTemplate for said service is used to provide the location of the proxy servers(s) and allows for multiple implementations, each with a different level of functionality. The service can reference a tModel that identifies the service as providing proxy auto-config information. There are different tModels for each implementation alternative: 1. In the simplest case, the 'accessPoint' member of the bindingTemplate points directly to the proxy server. In this case, the client simply searches the UDDI registry for services that reference the Simple Proxy Auto-Config tModel. When one is found, the accessPoint of the bindingTemplate for that service points directly to the proxy to use and the client configures itself to use that proxy. 2. A second alternative is for the accessPoint to point to an Extensible Markup Language (XML) file that contains one or more proxy servers.