Web dispatch service

• US 7,499,983 B2
• Filed: 05/06/2002
• Issued: 03/03/2009
• Est. Priority Date: 05/06/2002
• Status: Expired due to Term

• Current Assignee: Micron Technology, Inc.
• Original Assignee: Micron Technology, Inc.
• Inventors: Acree, Don, Gore, Brooklin J., Chipman, Rian, Kickel, Craig
• Primary Examiner(s): Lin; Kenny S
• Application Number:
  US10/140,347
• Publication Number:
  US 20030208563A1
• Time in Patent Office: 2,493 Days
• Field of Search: 709/217, 709/219
• US Class Current: 709/219
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/563 Data redirection of data network streams
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

A system and method for accessing an application server includes sending a service command from a requestor to a dispatch server, processing the service command on the dispatch server, translating the service command on the dispatch server into an application request to the application server, wherein the translating is based on a service definition stored on the dispatch server, and processing the application request. In one embodiment, the dispatch server includes a dispatch processor that is further programmed to manage a user interface, wherein the user interface includes a service registration interface, a service modification interface, and a service deletion interface.

Claims

1. A dispatch server comprising:

a data store having one or more application service definitions, wherein each application service definition includes a service name and one or more service data entries for a service registered with the dispatch server and located on an application server coupled to the data store; and

a dispatch processor operatively coupled to the data store, wherein the dispatch processor is programmed to translate a service request into an application request, the service request being received from a client and including a name of the dispatch server that is provided by the client and a name of the service registered with the dispatch server, wherein the translation is at least partially based on one of the application service definitions, wherein the dispatch processor is to redirect the application request back to the client without processing the application request and without sending the application request to the application server having the service to be invoked by the service request; and

wherein the application request includes only the application request relevant to the service to be invoked by the service request.

2. The dispatch server of claim 1, wherein the dispatch processor is further programmed to subsequently translate the service request into a different application request, wherein the subsequent translation is at least partially based on a changed application service definition.

3. The dispatch server of claim 1, wherein the dispatch processor is further programmed to manage a user interface, wherein the user interface includes a service registration interface, a service modification interface, and a service deletion interface.

4. The dispatch server of claim 1, wherein the dispatch server is located on the World Wide Web.

20. The dispatch server of claim 1, wherein the application request includes a complex address.

5. A method for accessing an application owner, the method comprising:

receiving a service command from a requestor at a dispatch server, the service command including a name of the dispatch server that is provided by the requestor and a service name for a service registered with the dispatch server;

processing the service command on the dispatch server;

translating the service command on the dispatch server into an application request, wherein the translation is at least partially based on a service definition stored on the dispatch server; and

redirecting the application request to the requestor without processing the application request at the dispatch server and without sending the application request from the dispatch server to an application server having the service to be invoked by the service command, wherein redirecting the application request includes sending only the application request relevant to the service to be invoked by the service request.

6. The method of claim 5, further comprising sending the application request from the requestor to the application owner.

7. The method of claim 5, wherein the processing of the application request comprises:

sending the application request from the dispatch server to the application owner;

sending an application response from the application owner to the dispatch server; and

sending the application response from the dispatch server to the requestor.

8. The method of claim 5, wherein the processing of the service command includes validating the service command, and checking the service command for parameters.

9. The method of claim 5, wherein the service command includes a Universal Resource Locator.

10. A method for accessing a complex web link, the method comprising:

receiving a service request from an end-user at a dispatch server, the service request including a name of the dispatch server that is provided by the end user and a service name for a service registered with the dispatch server;

translating the service request into a complex application command, wherein the translating is at least partially based on a service definition stored on the dispatch server;

redirecting the complex application command from the dispatch server to the end-user without processing the complex application command at the dispatch server and without sending the complex application command from the dispatch server to a service provider having the service to be invoked by the service request, and wherein redirecting the complex application command includes sending the complex application command relevant to the service to be invoked by the service request;

sending the complex application command from the end-user to the service provider; and

sending an application response from the service provider to the end-user.

11. A system comprising:

a dispatch server comprising;

a data store; and

a processor programmed to translate a service request into an application command, wherein the translation is at least partially based on a service definition stored in the data store and the processor is operable to redirect the application command back to a service user operatively coupled to the dispatch server without processing the application command and without sending the application command to an application server having a service to be invoked by the service command, wherein the application command includes only the application command relevant to the service to be invoked by the service command; and

wherein the service user sends the service request to the dispatch server, wherein the service request includes a name of the dispatch server that is provided by the service user and a service name for a service registered with the dispatch server, and wherein the dispatch server translates the service request and redirects the application command to the service user.

12. The system of claim 11, wherein the system is located on the World Wide Web.

13. The system of claim 11, wherein the system further includes an independent service management server.

14. The system of claim 13, wherein the independent service management server includes a processor programmed to manage a service registration interface, a service modification interface, and a service deletion interface.

15. A computer-readable medium having instructions stored thereon to perform a computerized method comprising:

receiving a service invocation from an end-user to a dispatch server, the service invocation including a name of the dispatch server that is provided by the end user and a service name for a service registered with the dispatch server;

processing the service invocation on the dispatch server;

translating the service invocation on the dispatch server into an application command, wherein the translating is at least partially based on a service definition stored on the dispatch server; and

redirecting the application command to the end-user without processing the application command at the dispatch server and without sending the application command from the dispatch server to an application server having the service to be invoked by the service invocation, wherein redirecting includes sending only the application command relevant to the service to be invoked by the service invocation.

16. The computer-readable medium of claim 15, wherein the processing of the service invocation includes validating the service invocation.

17. The computer-readable medium of claim 15, wherein the processing of the service invocation includes checking the service invocation for parameters.

18. A method for source routing on a web dispatch server, the method comprising:

sending a service command from a requestor at the web dispatch server, the service command including a name of the web dispatch server that is provided by the requestor and a service name for a service registered with the web dispatch server;

determining which application server that provides the requested service is geographically closest to the requestor;

translating the service command into an application request, wherein the translating is at least partially based on the determination of the geographically closest application server; and

redirecting the application request back to the requestor without processing the application request and without sending the application request to the application server having the service to be invoked by the service request, wherein the application request includes only the application request relevant to the service to be invoked by the service request.

19. A computer-readable medium having instructions stored thereon, which when executed by a computer, cause the computer to perform a computerized method comprising:

receiving a service request from a requestor at a dispatch server, the service request including a name of the dispatch server and a registered service name that is provided by the requestor and a service name for a service registered with the dispatch server;

validating the service request;

checking the service request for parameters;

translating the service request on the dispatch server into an application request to an application server, wherein the translating is at least partially based on a service definition stored on the dispatch server; and

redirecting the application request back to the requestor without processing the application request at the dispatch server and without sending the application request from the dispatch server to an application server having the service to be invoked by the service request, wherein the application request includes only the application request relevant to the service to be invoked by the service request.