2.2.1.13.5 Content Tag Knowledge
The Content Tag Knowledge specifies changes to implementer-defined content that is stored on the server. The Content Tag Knowledge has the following format.
Content Tag Knowledge is intended to be used for server-specific optimizations. Clients MUST NOT interpret the values as they are not defined by this protocol.
Client considerations:
That these properties MUST NOT be modified by the client.
These values SHOULD be considered opaque from the client's perspective and the client SHOULD NOT attempt to interpret the values.
They MUST be sent back to the server unmodified.
Server considerations.
Server implementations do not need to replicate the same logic and behavior as SharePoint when using these properties to decide which cells to send to the client.
Because the values are opaque to the client, a server implementation can use these values as needed.
It has the following format.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Content Tag Knowledge Start |
Content Tag Entry Knowledge Array (variable) |
||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
Content Tag Knowledge End |
|||||||||||||||||||||||||||||||
Content Tag Knowledge Start (2 bytes): A 16-bit Stream Object Header (section 2.2.1.5.1) that specifies the Content Tag Knowledge start.
Content Tag Knowledge Entry Array (variable): An array of Content Tag Knowledge Entry structures (section 2.2.1.13.5.1), each of which specifies changes for a BLOB.
Content Tag Knowledge End (1 byte): An 8-bit Stream Object Header (section 2.2.1.5.3) that specifies the Content Tag Knowledge end.