US6457066B1
Expired / Lapsed
US
⏱️ 0.0 years remaining
Simple object access protocol
Assignee: INMENTIA IPH Inc
•
Filing: 1997-11-10
•
Granted: 2002-09-24
•
Expires: 2017-11-10
Abstract
Abstract An application layer protocol is provided on top of HTTP 1.0/1.1 to allow for COM Automation objects to be invoked over the Internet through IIS/ISAPI servers. The format essentially encodes the automation object's name, method to invoke, and any [in], [out], [in, out] parameters that the method signature requires, packages them up into a custom MIME type and marshals it to the ISAPI dynamic link library (DLL) on the IIS/HTTP server. There, the ISAPI DLL contains the logic to unpack the SOAP request, parses it, creates the Automation object, invokes the method with the marshaled parameters, and then returns any [out] parameters to the caller/client using the SOAP protocol. It is a stateless protocol, meaning that object lifetimes only extend to one method, and are recreated between multiple calls to the object.
Inventors
- 👤 Gunnar Mein
- 👤 Shankar Pal
- 👤 Govinda Dhondu
- 👤 Thulusalamatom Krishnamurthi Anand
- 👤 Alexander Stojanovic
- 👤 Mohsen Al-Ghosein
- 👤 Paul M. Oeuvray
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-02 05:37
CPC Classifications
G; G06; G06F; G06F9/00; G06F9/06; G06F9/46; G06F9/54; G06F9/547
Claims Analysis
Total Claims: 5
Claim 1
Independent Claim
142 words
A computer-readable medium have stored thereon a data structure for marshaling data between a client computer and a server computer through the Internet, wherein the marshaled data is associated with a method of an Automation object to be instantiated on the server computer, the data structure comprising: (a) a header section comprising: (1) a first header data field containing data representing a name (progid) of the Automation object to be instantiated on the server computer; (2) a second header data field containing data representing a name of a method of the Automation object to invoke; (b) a body section comprising: (1) at least one first body data field containing data representing input parameters for the method to process: and (c) a trailer section comprising a checksum value; wherein (d) the data structure is packaged as an HTTP message in multipart MIME packets.
Claim 2
Dependent Claim
142 words
A computer-readable medium have stored thereon a data structure for marshaling data between a client computer and a server computer through the Internet, wherein the marshaled data is associated with a method of an Automation object to be instantiated on the server computer, the data structure comprising: (a) a header section comprising: (1) a first header data field containing data representing a name (progid) of the Automation object to be instantiated on the server computer; (2) a second header data field containing data representing a name of a method of the Automation object to invoke; (b) a body section comprising: (1) at least one first body data field containing data representing input parameters for the method to process: and (c) a trailer section comprising a checksum value; wherein (d) the data structure is packaged as an HTTP message in multipart MIME packets.
Claim 3
Dependent Claim
72 words
The data structure of claim 1 , wherein: (a) the data structure is for marshaling data from the client computer to the server computer, and is packaged as an HTTP POST message; and wherein (b) the header comprises a third header data field containing data representing an HTTP POST request, and a fourth header data field containing data representing a name of an Applications Programming Interface (API) for unpackaging multipart MIME packets.
Claim 4
Dependent Claim
26 words
The data structure of claim 2 , wherein the header further comprises a fifth header data field containing data representing an identifier of an HTTP version.
Claim 5
Dependent Claim
86 words
The data structure of claim 1 , wherein: (a) the data structure is for marshaling data from the server computer to the client computer, and is packaged as an HTTP Response message; (b) the header section comprises a third header data field containing data representing an identifier of an HTTP version, and a fourth header data field containing data representing a status code; and wherein (c) the body section further comprises at least one second body data field containing data representing return parameters from the method.
References Cited (Backward Citations)
US5548723A
Cited
US5491800A
Cited
US5956509A
Cited
US5938733A
Cited
US5956483A
Cited
US6052710A
Cited
US6125352A
Cited
US5931917A
Cited
US5991802A
Cited
US6370561B1
Cited
US5987504A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2005-09-23 | 2006-03-25 | 2006-09-24 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2009-09-23 | 2010-03-25 | 2010-09-24 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2013-09-23 | 2014-03-25 | 2014-09-24 | $7700.00 | Window Closed / Lapsed |