US7996499B2 - Intelligent processing of web service requests for backward compatibility - Google Patents
Intelligent processing of web service requests for backward compatibility Download PDFInfo
- Publication number
- US7996499B2 US7996499B2 US12/479,858 US47985809A US7996499B2 US 7996499 B2 US7996499 B2 US 7996499B2 US 47985809 A US47985809 A US 47985809A US 7996499 B2 US7996499 B2 US 7996499B2
- Authority
- US
- United States
- Prior art keywords
- web service
- service request
- binding properties
- computer
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
Definitions
- Web service technologies allow client programs to access functionality provided by compatible Web services.
- the functionality exposed by the Web services can be accessed remotely through a data communications network, such as the Internet.
- Web service technologies utilized to implement Web services and compatible client programs are frequently upgraded. Consequently, it may become necessary for a software developer to maintain a Web service and one or more compatible client programs for several different versions of a Web service technology. Alternately, the developer might upgrade the Web service and the client programs to the newer version of the Web service technology. However, each of these alternatives can be costly and time consuming for the developer.
- Newer Web service technologies typically provide a mechanism for handling Web service requests constructed according to an older version of the Web service technology.
- the Web service converts Web service requests compatible with an older version of a Web service technology for compatibility with a newer version of the Web service technology prior to processing the requests. Conversion of Web service requests in this manner, however, can impose significant undesirable processing overhead.
- Web service requests constructed according to an older version of a Web service technology (which may be referred to herein as a “legacy” Web service technology) can be processed without modifying a legacy Web service client utilized to construct the request.
- legacy Web service technology which may be referred to herein as a “legacy” Web service technology
- requests can be handled in a manner that minimizes the processing performed on the Web service request prior to forwarding the request to the target Web service, such as converting the Web service request for compatibility with a newer version of the Web service technology.
- a Web service client constructs a Web service request in accordance with a legacy Web service technology.
- the Web service request targets a Web service that is also compatible with the legacy Web service technology.
- the Web service request might target an activation file constructed in accordance with the legacy Web service technology.
- the Web service request and the targeted activation file are constructed in accordance with the Active Server Methods X (“ASMX”) Web service technology from MICROSOFT CORPORATION of Redmond, Wash.
- ASMX Active Server Methods X
- a Web service In order to process a Web service request constructed with a legacy Web service technology, a Web service is implemented using a newer Web service technology that is capable of producing the same results as the Web service compatible with the legacy Web service technology given the same parameters.
- the Web service is constructed using the Windows Communication Foundation (“WCF”) Web service technology.
- the Web service request is modified so that it targets the Web service implemented using the newer Web service technology. For instance in one implementation, if the Web service request targets an activation file for the legacy Web service technology, the Web service request is modified such that it targets an activation file for the Web service constructed according to the newer Web service technology.
- Web service requests may be modified in a manner that minimizes the processing performed on the Web service request prior to forwarding the request to the target Web service.
- binding properties define aspects of a binding between the Web service request and the Web service. For instance, an encoding type for the Web service request, a message version utilized to format the Web service request, and a transport utilized to transmit the Web service request may be identified. Binding properties supported by the target Web service are also identified.
- Binding properties for use when forwarding the Web service request to the target Web service are then selected based upon the binding properties associated with the Web service request and supported by the target Web service.
- the binding properties are selected as to minimize the processing performed on the Web service request prior to forwarding the Web service request to the target Web service. For instance, the binding properties might be selected in order to avoid re-encoding the Web service request or to avoid a conversion of the Web service request to a different message version. Once the binding properties have been selected, the binding properties are utilized to forward the Web service request to the target Web service.
- FIG. 1 is a computer network and software architecture diagram that shows aspects of an illustrative operating environment and several software components presented herein;
- FIG. 2 is a flow diagram showing aspects of the operation of a uniform resource locator (“URL”) rewriter provided hereby and utilized in embodiments disclosed herein;
- URL uniform resource locator
- FIG. 3 is a computer network and software architecture diagram showing aspects of the operation of an intermediary provided hereby and utilized in embodiments presented herein;
- FIG. 4 is a flow diagram showing aspects of the operation of an intermediary according to one embodiment presented herein;
- FIG. 5 is a computer architecture diagram showing an illustrative computer hardware and software architecture for a computing system capable of implementing aspects of the embodiments presented herein.
- FIG. 1 is a computer network and software architecture diagram that shows aspects of an illustrative operating environment and several software components presented herein.
- FIG. 1 shows several client computers 102 A- 102 B that are configured with Web service client applications operative to transmit Web service requests to one or more Web services.
- Web service technologies allow client programs to access functionality provided by compatible Web services. The functionality exposed by the Web services can be accessed remotely through a data communications network, such as the Internet. Accordingly, it should be appreciated that the computing systems and software components illustrated in FIG. 1 may communicate with one another through the use of one or more data communications networks (not shown in FIG. 1 ).
- server computers are illustrated in FIG. 1 , it should be appreciated that more or fewer computer systems may be utilized than illustrated in FIG. 1 and described herein.
- the client computers 102 A- 102 B are configured to execute Web service client applications that have been programmed according to different Web service technologies.
- the client computer 102 A is configured to execute an Active Server Methods X (“ASMX”) Web service client application 106 A.
- ASMX Web service client application 106 A has been programmed for compatibility with the ASMX Web service technology from MICROSOFT CORPORATION of Redmond, Wash. Accordingly, the ASMX Web service client application 106 A issues Web service requests, such as the ASMX Web service request 108 A, that are compatible with the ASMX Web service technology.
- the ASMX Web service technology may also be referred to herein as a legacy Web service technology as this Web service technology has been superseded by the WINDOWS Communication Foundation (“WCF”) Web service technology, also from MICROSOFT CORPORATION.
- WCF WINDOWS Communication Foundation
- the client computer 102 B is configured in one embodiment to execute a WCF Web service client application 106 B that has been programmed for compatibility with the WCF technology.
- the WCF Web service client application 106 B issues Web service requests, such as the WCF Web service request 108 B, that are compatible with WCF.
- the ASMX Web service request 108 A targets a compatible Web service, such as the ASMX Web service 118 A.
- the WCF Web service request 108 B targets a WCF Web service 118 B.
- the ASMX Web service request 108 A targets an ASMX activation file 116 A.
- the ASMX activation file 116 A is a file that allows a Web server application 110 to identify the particular ASMX Web service 118 A to handle a particular ASMX Web service request 108 A.
- the WCF Web service request 108 B may target a WCF activation file 116 B.
- the WCF activation file 116 B allows the Web server application 110 to determine the particular Web service, such as the WCF Web service 118 B, for handling the WCF Web service request 108 B.
- the WCF Web service 118 B is programmed to provide the same results as the ASMX Web service 118 A given the same set of inputs.
- the WCF Web service 118 B is programmed for compatibility with the WCF technology while the ASMX Web service 118 A is programmed for compatibility with the ASMX Web service technology.
- the embodiments presented herein describe mechanisms that permit the WCF Web service 118 B to process the ASMX Web service request 108 A in an efficient manner. This allows a developer to discontinue maintenance of the ASMX activation file 116 A and the ASMX Web service 118 A while still servicing Web service requests from the ASMX Web service client application 106 A. Additional details regarding the technologies provided herein for enabling the WCF Web service 118 B to handle the ASMX Web service request 108 A will be provided below.
- a Uniform Resource Locator (“URL”) rewriter 112 is provided.
- the URL rewriter 112 provides functionality for modifying Web service requests that have been constructed using a legacy Web service technology to target a compatible Web service implemented using a newer Web service technology. For instance, in one implementation, if the URL rewriter 112 receives a Web service request that targets an activation file for a legacy Web service technology, the Web service request will be modified by the URL rewriter 112 such that it targets an activation file for the Web service constructed according to the newer Web service technology.
- FIG. 1 illustrates this mechanism according to one particular implementation.
- the URL rewriter 112 operates in conjunction with a Web server application 110 .
- the URL rewriter 112 operates in conjunction with a processing pipeline utilized by the Web server application 110 .
- the URL rewriter 112 can process Web service requests prior to the processing performed by the Web server application 110 .
- the URL rewriter 112 can process incoming Web service requests, such as the ASMX Web service request 108 A and the WCF Web service request 108 B, to target an appropriate Web service.
- the URL rewriter 112 receives an ASMX Web service request 108 A from the ASMX Web service client application 106 A.
- the ASMX Web service request 108 A includes a request for the ASMX Web service 118 A by targeting the ASMX activation file 116 A.
- the URL rewriter 112 is configured to modify the ASMX Web service request 108 A to target an activation file for a Web service constructed according to a newer Web service technology.
- the URL rewriter 112 modifies the ASMX Web service request 108 A to form a modified ASMX Web service request 114 that targets the WCF activation file 116 B.
- the modified ASMX Web service request 114 is then provided to the Web server application 110 which, in turn, provides the modified ASMX Web service request 114 to the WCF activation file 116 B.
- the ASMX Web service request 108 A is modified such that it is serviced by the WCF Web service 118 B.
- the URL rewriter 112 may also receive a WCF Web service request 108 B. If such a request is received, the URL rewriter 112 takes no action with respect to the WCF Web service request 108 B. Instead, the WCF Web service request 108 B is passed directly to the Web server application 110 which, in turn, provides the WCF Web service request 108 B to the WCF activation file 1116 B. In this way, the WCF Web service request 108 B is processed by the WCF Web service 118 B in a typical fashion.
- the URL rewriter 112 provides functionality for modifying an ASMX Web service request 108 A or another type of legacy Web service request to target a WCF Web service 118 B or another Web service constructed using a newer Web service technology.
- the WCF technology provides functionality for handling a legacy Web service request, the processing performed by the WCF technology may be inefficient. Accordingly, the embodiments presented herein also include a mechanism for processing legacy Web service requests in a more efficient manner. Details regarding this mechanism are provided below with respect to FIGS. 3-4 .
- FIG. 1 shows a server computer 104 A executing the URL rewriter 112 and the Web server application 110 and a server computer 104 B executing the Web services 118 A and 118 B
- the functionality shown in FIG. 1 may be deployed across a single computer or more computers than shown in FIG. 1 .
- FIG. 1 shows a server computer 104 A executing the URL rewriter 112 and the Web server application 110 and a server computer 104 B executing the Web services 118 A and 118 B
- the functionality shown in FIG. 1 may be deployed across a single computer or more computers than shown in FIG. 1 .
- FIG. 1 shows a server computer 104 A executing the URL rewriter 112 and the Web server application 110 and a server computer 104 B executing the Web services 118 A and 118 B
- FIG. 1 shows a server computer 104 A executing the URL rewriter 112 and the Web server application 110 and a server computer 104 B executing the Web services 118 A and 118 B
- FIG. 2 is a flow diagram showing a routine 200 that illustrates aspects of the operation of the URL rewriter 112 according to one embodiment presented herein.
- the logical operations described herein are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance and other requirements of the computing system. Accordingly, the logical operations described herein are referred to variously as states operations, structural devices, acts, or modules. These operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof. It should also be appreciated that more or fewer operations may be performed than shown in the figures and described herein. These operations may also be performed in a different order than those described herein.
- the routine 200 begins at operation 202 , where the URL rewriter 112 determines whether a Web service request has been received. If a Web service request has not been received, the routine 200 proceeds to operation 202 , where another such determination is made. If a Web service request has been received, the routine 200 proceeds to operation 204 where the URL rewriter 112 determines whether the received Web service request was an ASMX Web service request, such as the ASMX Web service request 108 A.
- the routine 200 branches to operation 208 where the URL rewriter 112 provides the received Web service request to the Web server application 110 .
- the URL rewriter 112 does nothing with the request if it is not an ASMX Web service request.
- the Web server application 110 handles the request in a normal manner as appropriate based on the request type, including providing the request to WCF for handling. From operation 208 , the routine 200 proceeds to operation 202 , described above.
- the routine 200 proceeds from operation 204 to operation 206 .
- the URL rewriter 112 modifies the ASMX Web service request 108 A to target the WCF activation file 116 B instead of the ASMX activation file 116 A. As discussed above, this causes the WCF Web service 118 B to handle the ASMX Web service request 108 A rather than the ASMX Web service 118 A.
- routine 200 proceeds to operation 208 where the URL rewriter provides the modified ASMX Web service request 114 to the Web server application 110 which, in turn, provides the modified ASMX Web service request 114 to the WCF activation file 116 B. From operation 208 , the routine 200 proceeds to operation 202 , described above.
- the functionality of the URL rewriter 112 has been described in the context of the legacy ASMX Web service technology and the newer WCF technology, the functionality of the URL rewriter 112 may be applied to any type of Web service technologies that support a compatibility path and URL rewriting in the manner presented herein.
- FIG. 3 a computer network and software diagram will be described that shows aspects of the operation of an intermediary 302 provided hereby and utilized in embodiments presented herein.
- the intermediary 302 provides functionality for modifying Web service requests in a manner that minimizes the processing performed on the Web service requests prior to forwarding the requests to a target Web service.
- the intermediary 302 may comprise a software component executed by the server computer 104 A, the server computer 104 B, or another type of server computer. As will be described in greater detail below, the intermediary 302 processes Web service requests prior to forwarding the Web service request to the target Web service in order to reduce the amount of processing performed by the target Web service on the Web service request.
- a Web service request 108 may be generated and forwarded to a Web server application 110 .
- the Web service request 108 shown in FIG. 3 may comprise an ASMX Web service request, a WCF Web service request, or a Web service request constructed utilizing another type of Web service technology.
- the Web server application 110 is configured to provide the Web service request 108 to the intermediary 302 .
- the intermediary 302 is configured to identify one or more binding properties associated with the Web service request 108 .
- the binding properties define aspects of the Web service request 108 and the mechanism utilized to transmit the Web service request 108 .
- the binding properties might define an encoding type for the Web service request, a message version utilized to format the Web service request 108 , and the type of transport utilized to transmit the Web service request.
- the encoding type for the Web service request 108 might include text, binary, and other types of encodings.
- the message version utilized to format the Web service request 108 may comprise different versions of the Simple Object Access Protocol (“SOAP”) or other types of messaging versions and formats.
- SOAP Simple Object Access Protocol
- the intermediary 302 is also configured to identify binding properties supported by the target Web service.
- the target Web service is the WCF Web service 118 B.
- the intermediary 302 is configured to identify the binding properties supported by the WCF Web service 118 B.
- the intermediary 302 may identify the encoding supported by the WCF Web service 118 B, the message versions supported by the WCF Web service 118 B, and the transport types supported by the WCF Web service 118 B.
- the transport types might include, for instance, the transmission control protocol (“TCP”), hypertext transport protocol (“HTTP”), a WCF named pipe binding, or another type of transport mechanism.
- the intermediary 302 is further configured to identify binding properties 304 for use when forwarding the Web service request 108 to the WCF Web service 118 B.
- the binding properties 304 are selected as to minimize the processing performed on the Web service request by the WCF Web service 118 B.
- the intermediary 302 might select binding properties 304 in order to avoid causing the intermediary 302 to re-encode the Web service request 108 prior to processing.
- the intermediary 302 might select the binding properties 304 (e.g. encoding and message version) in a manner as to avoid requiring a conversion of the Web service request 108 to a different message version.
- the Web service request 108 might be formatted using text encoding and the SOAP 1.1 message version. If the intermediary 302 determines that the WCF Web service 118 B supports text encoding and the SOAP 1.1 message version, then the binding properties 304 will be selected to include the SOAP 1.1 message version and text encoding. In this manner, the Web service request 108 can be forwarded directly to the Web service 118 B without processing by the intermediary 302 or the WCF Web service 118 B. If, however, the WCF Web service 118 B only supports the SOAP 1.2 message version or does not support text encoding, then the intermediary 302 will select binding properties 304 most compatible with the binding properties supported by the WCF Web service 118 B.
- the intermediary 302 will also convert the Web service request 108 for use with the selected binding properties 304 .
- the intermediary 302 might convert the Web service request 108 to a SOAP version supported by the WCF Web service 118 B or re-encode the Web service request 108 in an encoding type supported by the WCF Web service 118 B. Additional details regarding this process will be provided below.
- the intermediary 302 provides the Web service request 108 to the target Web service.
- a WCF activation file 116 B is utilized to target the WCF Web service 108 B. Accordingly, the WCF activation file 116 B is utilized to identify and instantiate the target WCF Web service 118 B.
- the WCF Web service 118 B performs the processing requested by the Web service request 108 and generates a Web service response 306 .
- the Web service response 306 is the response to the Web service request 108 .
- the intermediary 302 In response to receiving the Web service response 306 , the intermediary 302 performs processing on the Web service response 306 in order to ensure that the Web service response 306 is compatible with the calling Web service client application. For instance, if the intermediary 302 converted the Web service request 108 between message versions or to utilize a different encoding, the intermediary 302 will perform a reverse conversion on the Web service response 306 prior to providing the Web service response 306 to the Web server application 110 . When the Web server application 110 receives the Web service response 306 from the intermediary 302 , the Web server application 110 provides the Web service response 306 to the calling Web service client application as a response to the original Web service request 108 . Additional details regarding this process will be provided below with respect to FIG. 4 .
- FIG. 4 an illustrative routine 400 will be described that illustrates the operation of intermediary 302 according to one embodiment presented herein.
- the processing shown in FIG. 4 is performed by the intermediary 302 in response to receiving a Web service request 108 from a Web service client application, such as the ASMX Web service client application 106 A or the WCF Web service client application 106 B.
- a Web service client application such as the ASMX Web service client application 106 A or the WCF Web service client application 106 B.
- the routine 400 begins at operation 402 where the intermediary 302 identifies the message version for the received Web service request.
- the message version might comprise a SOAP message version or a message version utilized by another type of protocol.
- the routine 400 then proceeds to operation 404 , where the intermediary 302 identifies the encoding type utilized to encode the received Web service request.
- the encoding type might include binary encoding, text encoding, or another type of encoding known to those skilled in the art. It should be appreciated that although the message version and encoding type are described herein as illustrative binding properties, the intermediary 302 may be configured to identify other binding properties associated with a Web service request in a similar fashion.
- the routine 400 proceeds to operation 406 where the intermediary 302 identifies binding properties supported by the target Web service 118 .
- the intermediary 302 might be configured to identify the message version, encoding types, and transports supported by the Web service targeted by the received Web service request. Once the binding properties associated with the Web service request 108 and the targeted Web service have been identified, the routine 400 proceeds to operation 408 .
- the intermediary 302 selects a binding with the requested binding properties 304 for use in forwarding the received Web service request to the target Web service.
- a binding is selected having binding properties 304 that minimize the processing of the Web service request 108 prior to forwarding the Web service request to the Web service.
- a binding may be selected with binding properties 304 that minimize the need to convert the Web service request 108 between message versions or encoding types.
- the routine 400 proceeds to operation 410 , where the intermediary 302 determines whether processing of the Web service request 108 is needed. For instance, depending on the binding properties 304 that have been selected, the intermediary 302 may convert the Web service request 108 to another message version or encoding type. If such processing is not needed, the routine 400 proceeds from operation 410 to operation 414 . If processing of the Web service request 108 is needed, the routine 400 proceeds from operation 410 to operation 412 .
- the intermediary 302 performs the processing on the Web service request 108 . For instance, as discussed above, the intermediary 302 might convert the Web service request 108 between message types or to a different form of encoding. Once the processing has been completed by the intermediary 302 , the intermediary 302 forwards the processed Web service request to the target Web service utilizing the selected binding properties 304 . From operation 414 , the routine 400 proceeds to operation 402 , described above.
- FIG. 5 shows an illustrative computer architecture for a computer 500 capable of executing the software components described herein for optimized routing in the manner presented above.
- the computer architecture shown in FIG. 5 illustrates a conventional desktop, laptop, or server computer and may be utilized to execute any aspects of the software components presented herein.
- the computer architecture shown in FIG. 5 includes a central processing unit 502 (“CPU”), a system memory 508 , including a random access memory 514 (“RAM”) and a read-only memory (“ROM”) 516 , and a system bus 504 that couples the memory to the CPU 502 .
- the computer 500 further includes a mass storage device 510 for storing an operating system 518 , application programs, and other program modules, which are described in greater detail herein.
- the mass storage device 510 is connected to the CPU 502 through a mass storage controller (not shown) connected to the bus 504 .
- the mass storage device 510 and its associated computer-readable media provide non-volatile storage for the computer 500 .
- computer-readable media can be any available computer storage media that can be accessed by the computer 500 .
- computer-readable media may include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data.
- computer-readable media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), HD-DVD, BLU-RAY, or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 500 .
- the computer 500 may operate in a networked environment using logical connections to remote computers through a network such as the network 520 .
- the computer 500 may connect to the network 520 through a network interface unit 506 connected to the bus 504 . It should be appreciated that the network interface unit 506 may also be utilized to connect to other types of networks and remote computer systems.
- the computer 500 may also include an input/output controller 512 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in FIG. 5 ). Similarly, an input/output controller may provide output to a display screen, a printer, or other type of output device (also not shown in FIG. 5 ).
- a number of program modules and data files may be stored in the mass storage device 510 and RAM 514 of the computer 500 , including an operating system 518 suitable for controlling the operation of a networked desktop, laptop, or server computer.
- the mass storage device 510 and RAM 514 may also store one or more program modules.
- the mass storage device 510 and the RAM 514 may store the URL rewriter 112 and the intermediary 302 , each of which was described in detail above with respect to FIGS. 1-4 .
- the mass storage device 510 and the RAM 514 may also store other types of program modules and data.
- the software components described herein may, when loaded into the CPU 502 and executed, transform the CPU 502 and the overall computer 500 from a general-purpose computing system into a special-purpose computing system customized to facilitate the functionality presented herein.
- the CPU 502 may be constructed from any number of transistors or other discrete circuit elements, which may individually or collectively assume any number of states. More specifically, the CPU 502 may operate as a finite-state machine, in response to executable instructions contained within the software modules disclosed herein. These computer-executable instructions may transform the CPU 502 by specifying how the CPU 502 transitions between states, thereby transforming the transistors or other discrete hardware elements constituting the CPU 502 .
- Encoding the software modules presented herein may also transform the physical structure of the computer-readable media presented herein.
- the specific transformation of physical structure may depend on various factors, in different implementations of this description. Examples of such factors may include, but are not limited to: the technology used to implement the computer-readable media, whether the computer-readable media is characterized as primary or secondary storage, and the like.
- the computer-readable media is implemented as semiconductor-based memory
- the software disclosed herein may be encoded on the computer-readable media by transforming the physical state of the semiconductor memory.
- the software may transform the state of transistors, capacitors, or other discrete circuit elements constituting the semiconductor memory.
- the software may also transform the physical state of such components in order to store data thereupon.
- the computer-readable media disclosed herein may be implemented using magnetic or optical technology.
- the software presented herein may transform the physical state of magnetic or optical media, when the software is encoded therein. These transformations may include altering the magnetic characteristics of particular locations within given magnetic media. These transformations may also include altering the physical features or characteristics of particular locations within given optical media, to change the optical characteristics of those locations. Other transformations of physical media are possible without departing from the scope and spirit of the present description, with the foregoing examples provided only to facilitate this discussion.
- the computer 500 may comprise other types of computing devices, including hand-held computers, embedded computer systems, personal digital assistants, and other types of computing devices known to those skilled in the art. It is also contemplated that the computer 500 may not include all of the components shown in FIG. 5 , may include other components that are not explicitly shown in FIG. 5 , or may utilize an architecture completely different than that shown in FIG. 5 .
Abstract
Description
Claims (17)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/479,858 US7996499B2 (en) | 2009-06-08 | 2009-06-08 | Intelligent processing of web service requests for backward compatibility |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/479,858 US7996499B2 (en) | 2009-06-08 | 2009-06-08 | Intelligent processing of web service requests for backward compatibility |
Publications (2)
Publication Number | Publication Date |
---|---|
US20100312859A1 US20100312859A1 (en) | 2010-12-09 |
US7996499B2 true US7996499B2 (en) | 2011-08-09 |
Family
ID=43301518
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/479,858 Expired - Fee Related US7996499B2 (en) | 2009-06-08 | 2009-06-08 | Intelligent processing of web service requests for backward compatibility |
Country Status (1)
Country | Link |
---|---|
US (1) | US7996499B2 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104176301A (en) * | 2014-08-14 | 2014-12-03 | 浙江中烟工业有限责任公司 | Superspeed packer data acquisition system |
US20230101447A1 (en) * | 2021-09-20 | 2023-03-30 | Salesforce.Com, Inc. | Api gateway self paced migration |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10171593B2 (en) * | 2014-06-30 | 2019-01-01 | Verizon Patent And Licensing Inc. | Validating web services for compatibility with a client device by emulating the client device by populating a template associated with the web services |
US20120033583A1 (en) * | 2010-08-03 | 2012-02-09 | Hu Qingmin J | Policy-Based Network and Service Domain Selection for Legacy Non-IP Telecommunication Services Over Heterogeneous Networks |
EP3957445A1 (en) * | 2012-06-12 | 2022-02-23 | Snap-On Incorporated | An inventory control system having advanced functionalities |
CN108494606B (en) * | 2018-04-19 | 2020-12-15 | 四川师范大学 | WCF technology-based data service framework building method |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060136422A1 (en) * | 2004-12-20 | 2006-06-22 | Anatole Matveief | Multiple bindings in web service data connection |
US7117504B2 (en) * | 2001-07-10 | 2006-10-03 | Microsoft Corporation | Application program interface that enables communication for a network software platform |
US20070022007A1 (en) * | 2005-06-14 | 2007-01-25 | Mystorecredit.Com | System and method for a customer loyalty reward system utilizing a shopping search portal, a payment transfer agent and email marketing |
US20070067479A1 (en) * | 2005-09-21 | 2007-03-22 | Dimitar Angelov | Transport binding for a web services message processing runtime framework |
US20070220115A1 (en) * | 2006-03-17 | 2007-09-20 | Microsoft Corporation | Generating and binding web services to application components |
US7353464B1 (en) * | 2002-04-01 | 2008-04-01 | Microsoft Corporation | Hierarchical data navigation tool populated by a web service |
US7475403B2 (en) * | 2004-10-28 | 2009-01-06 | International Business Machines Corporation | Method for optimizing Web services binding |
US20090083211A1 (en) | 2006-10-10 | 2009-03-26 | Alok Sinha | Inferencing user interest |
US7577964B2 (en) * | 2003-02-28 | 2009-08-18 | Hewlett-Packard Development Company, L.P. | System and methods for defining a binding for web-services |
-
2009
- 2009-06-08 US US12/479,858 patent/US7996499B2/en not_active Expired - Fee Related
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7117504B2 (en) * | 2001-07-10 | 2006-10-03 | Microsoft Corporation | Application program interface that enables communication for a network software platform |
US20070100967A1 (en) | 2001-07-10 | 2007-05-03 | Microsoft Corporation | Application Program Interface for Network Software Platform |
US7353464B1 (en) * | 2002-04-01 | 2008-04-01 | Microsoft Corporation | Hierarchical data navigation tool populated by a web service |
US7577964B2 (en) * | 2003-02-28 | 2009-08-18 | Hewlett-Packard Development Company, L.P. | System and methods for defining a binding for web-services |
US7475403B2 (en) * | 2004-10-28 | 2009-01-06 | International Business Machines Corporation | Method for optimizing Web services binding |
US20060136422A1 (en) * | 2004-12-20 | 2006-06-22 | Anatole Matveief | Multiple bindings in web service data connection |
US20070022007A1 (en) * | 2005-06-14 | 2007-01-25 | Mystorecredit.Com | System and method for a customer loyalty reward system utilizing a shopping search portal, a payment transfer agent and email marketing |
US20070067479A1 (en) * | 2005-09-21 | 2007-03-22 | Dimitar Angelov | Transport binding for a web services message processing runtime framework |
US20070220115A1 (en) * | 2006-03-17 | 2007-09-20 | Microsoft Corporation | Generating and binding web services to application components |
US20090083211A1 (en) | 2006-10-10 | 2009-03-26 | Alok Sinha | Inferencing user interest |
Non-Patent Citations (15)
Title |
---|
"Alligator Tags", Retrieved at <<http://www.alligatortags.com/alligatortags-4-19-2008.html>>, Apr. 19, 2008, pp. 1-15. |
"Alligator Tags", Retrieved at >, Apr. 19, 2008, pp. 1-15. |
"Creating a WCF Service that Consumes an ASMX Service", Retrieved at <<http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/bdbbf515-7ea9-452a-b227-deda3aadcb89>>, Apr. 29, 2009, pp. 1-6. |
"Creating a WCF Service that Consumes an ASMX Service", Retrieved at >, Apr. 29, 2009, pp. 1-6. |
Birkby, Richard, "URL Rewriting with ASP.NET", Retrieved at <<http://www.codeproject.com/KB/aspnet/urlrewriter.aspx?fid=4228&df=90&mpp=25&noise=3&sort=Position&view=Quick&fr=101>>, Jul. 3, 2002, pp. 17. |
Joshi, Dipesh, "Convert Existing asmx .Net Web Service to WCF Service in .Net 3.0/3.5", Retrieved at <<http://archdipesh.blogspot.com/2008/02/convert-existing-asmx-net-web-service.html>>, Feb. 19, 2008, pp. 1-5. |
Joshi, Dipesh, "Convert Existing asmx .Net Web Service to WCF Service in .Net 3.0/3.5", Retrieved at >, Feb. 19, 2008, pp. 1-5. |
Kraak, Tom, "DNN URL Rewriter on Steroids", Retrieved at <<http://seablick.com/blog/91/dnn-url-rewriter-on-steroids.aspx>>, Jan. 16, 2008, pp. 1-2. |
Kraak, Tom, "DNN URL Rewriter on Steroids", Retrieved at >, Jan. 16, 2008, pp. 1-2. |
Lippard, Philip, "A New Generation of URL Rewriters ?", Retrieved at <<http://www.codeproject.com/KB/aspnet/nUrlRewriter1.aspx>>, Apr. 18, 2008, pp. 20. |
Lippard, Philip, "A New Generation of URL Rewriters ?", Retrieved at >, Apr. 18, 2008, pp. 20. |
Nberardi, "NET URL Rewriter and Reverse Proxy", Retrieved at <<http://code.msdn.microsoft.com/urlrewriter/Wiki/View.aspx?title=Home&version=6>>, Jan. 31, 2008, pp. 1-2. |
Nberardi, "NET URL Rewriter and Reverse Proxy", Retrieved at >, Jan. 31, 2008, pp. 1-2. |
Powell, Matt, "Web Services, Opaque Data, and the Attachments Problem", Retrieved at <<http://msdn.microsoft.com/en-us/library/ms996462.aspx>>, Jun. 2004, pp. 1-9. |
Powell, Matt, "Web Services, Opaque Data, and the Attachments Problem", Retrieved at >, Jun. 2004, pp. 1-9. |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104176301A (en) * | 2014-08-14 | 2014-12-03 | 浙江中烟工业有限责任公司 | Superspeed packer data acquisition system |
CN104176301B (en) * | 2014-08-14 | 2016-01-27 | 浙江中烟工业有限责任公司 | A kind of hyper-speed wrapping machine data acquisition system |
US20230101447A1 (en) * | 2021-09-20 | 2023-03-30 | Salesforce.Com, Inc. | Api gateway self paced migration |
US11914986B2 (en) * | 2021-09-20 | 2024-02-27 | Salesforce, Inc. | API gateway self paced migration |
Also Published As
Publication number | Publication date |
---|---|
US20100312859A1 (en) | 2010-12-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2805251B1 (en) | Managing script file dependencies and load times | |
US7996499B2 (en) | Intelligent processing of web service requests for backward compatibility | |
JP6949118B2 (en) | Blockchain service acceptance and consensus methods and devices | |
US7788290B2 (en) | Automatic file conversion to a target format | |
EP2791787B1 (en) | Autonomous network streaming | |
KR101941641B1 (en) | Efficiently providing multiple metadata representations of the same type | |
WO2019015272A1 (en) | Information processing method and device | |
US9286083B2 (en) | Satisfying missing dependencies on a running system | |
US9098316B2 (en) | Routing function calls to specific-function dynamic link libraries in a general-function environment | |
US8312048B2 (en) | Database application navigation | |
JP6418004B2 (en) | Event notification program, event notification method, and event notification device | |
US9853925B2 (en) | Automatic transformation of messages between service versions | |
US8166200B2 (en) | Smart routing | |
US8260944B2 (en) | Using a state machine embedded within a session initiation protocol (SIP) servlet to implement an application programming interface (API) | |
US9503489B2 (en) | Streaming data on data processes | |
US20140297736A1 (en) | Data interchange system | |
US9785560B2 (en) | Scene-isolated internet application | |
US9298449B2 (en) | Composite program history | |
US20210055971A1 (en) | Method and node for managing a request for hardware acceleration by means of an accelerator device | |
US20230297353A1 (en) | Intelligent data processing system with multi-interface frontend and backend | |
CN111274466A (en) | Non-structural data acquisition system and method for overseas server | |
CN111078324B (en) | Method and apparatus for prefetching page data | |
EP3872630B1 (en) | Request processing method and apparatus, electronic device, and computer storage medium | |
CN107911248B (en) | Upgrading method and device |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LEV, BOAZ;GARLICK, MICHAEL S.;REEL/FRAME:023223/0396 Effective date: 20090604 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034564/0001 Effective date: 20141014 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20230809 |