Pre-Grant Publication Number: 20080114839
Please help the USPTO examine the application by evaluating the relevance of the publicly submitted prior art to the patent application.
Peer-to-Patent forwards the Top 10 most relevant prior art submissions and their annotations to the United States Patent and Trademark Office.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Review this prior art and click on the thumbs up (or down) to indicate whether this submission should be forwarded to the USPTO.
If you login then you can add an annotation by typing in the box at the bottom of the screen to comment on the relevance of the prior art to the claims of the patent application.
Prior Art Detail
Summary / Description
| Summary / Description | Document 1 of 2, courtesy of Christopher R. Hertel, crh@samba.org |
Basic Information
| Type of Prior Art | Print Publication |
| Publication Title * | Microsoft Networks/OpenNET FILE SHARING PROTOCOL (INTEL Part Number 138446), Document Version 2.0, N |
| Author | |
| ISBN | |
| Page Range | |
| Medium | Book excerpt |
| Publication Date * | November 7, 1988 |
| URL | ftp://ftp.microsoft.com/develop... |
Notes / To Do
| Notes | |
Excerpt
Excerpt Chris writes: The oldest doc I have is "Microsoft Networks/OpenNET FILE SHARING PROTOCOL
(INTEL Part Number 138446), Document Version 2.0, November 7, 1988"
It lists NegProt, which seems to meet most of the description. |
Relevance
Claims
1
A method of version control for application message models, the method comprising:
establishing, on a message sending device, a sender message model, the sender message model specifying a message format for interpreting application messages, the sender message model comprising one or more sender field specifications, each sender field specification specifying a message field for storing data in an application message, each sender field specification comprising sender field characteristics;
calculating, by the message sending device, a sender version number for the sender message model in dependence upon the sender field characteristics of one or more of the sender field specifications of the sender message model;
creating, by the message sending device, an application message according to the sender message model; and
transmitting, by the message sending device to a message receiving device, the application message and the sender version number for the sender message model.
Relevance
The document describes negotiating a versioned protocol between a
client and a server application.
The document describes negotiating a versioned protocol between a
client and a server application.
Claim Chart
All
0 days left
