Method and apparatus for a paged update protocol

An apparatus comprising:

• at least one processor;
• and
• at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,
• generate, by a server device, an update document comprising one or more update statuses of one or more resources, wherein at least one of the one or more resources is identified using a respective obfuscation identifier based, at least in part, on a user identifier;
• divide the update document into a plurality of pages according to paged update protocol to produce linked page feeds that form the update document;
• archive the plurality of pages of the update document based, at least in part, on an expiration of the update document, a time interval, a schedule, on demand, or a combination thereof;
• receive a request from one or more subscribers for one of the one or more pages of the update document, or for one of the one or more archived pages of the update document based, at least in part, on whether the one or more subscriber's information is up to date;
• transmit the update document to the one or more subscribers;
• and
• transmit a feed of one or more obfuscation identifiers to the one or more subscribers,
• wherein the at least one of the one or more resources identified using the respective obfuscation identifier provides a second identifier of a universal resource locator (URL) where the plurality of pages of the update document is archived;
• and
• wherein each of the plurality of pages preceding an end page includes a corresponding relational link header that references the plurality of pages as a combined update document under the paged update protocol.

A method comprising:

• receiving a request from one or more subscribers for one or more pages of an update document, or for one or more archived pages of the update document based, at least in part, on whether the one or more subscriber's information is up to date;
• retrieving, at a client device, the update document comprising one or more update statuses of one or more resources, wherein at least one of the one or more resources is identified using a respective obfuscation identifier based, at least in part, on a user identifier, and wherein at least one of one or more resources identified using a respective obfuscation identifier provides a second identifier of a universal resource locator (URL) where the one or more pages of the update document is archived, the update document divided into a plurality of pages according to paged update protocol to produce linked page feeds that form the update document;
• determining whether one or more previously archived versions of the update document has been processed, wherein archiving the plurality of pages of the update document is based, at least in part, on an expiration of the update document, a time interval, a schedule, on demand, or a combination thereof;
• processing the update document, the one or more previously archived versions of the update document, or a combination thereof based, at least in part, on the determination,
• wherein the processing identifies at least one of the one or more update statuses for one or more resources of interest;
• and
• wherein each of the plurality of pages preceding an end page includes a corresponding relational link header that references the plurality of pages as a combined update document under the paged update protocol;
• transmitting the update document to the one or more subscribers;
• and
• transmitting a feed of one or more obfuscation identifiers to the one or more subscribers.

An apparatus comprising:

• at least one processor;
• and
• at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following,
• receive a request from one or more subscribers for one or more pages of an update document, or for one or more archived pages of the update document based, at least in part, on whether the one or more subscriber's information is up to date;
• retrieve, at a client device, the update document comprising one or more update statuses of one or more resources, wherein at least one of the one or more resources is identified using a respective obfuscation identifier based, at least in part, on a user identifier, and wherein at least one of one or more resources identified using a respective obfuscation identifier provides a second identifier of a universal resource locator (URL) where the update document is archived, the update document is divided into a plurality of pages according to paged update protocol to produce linked page feeds that form the update document;
• determine whether one or more previously archived versions of the update document has been processed, wherein archiving the plurality of pages of the update document is based, at least in part, on an expiration of the update document, a time interval, a schedule, on demand, or a combination thereof;
• process the update document, the one or more previously archived versions of the update document, or a combination thereof based, at least in part, on the determination,
• wherein the processing identifies at least one of the one or more update statuses for one or more resources of interest;
• and
• wherein each of the plurality of pages preceding an end page includes a corresponding relational link header that references the plurality of pages as a combined update document under the paged update protocol;
• transmit the update document to the one or more subscribers;
• and
• transmit a feed of one or more obfuscation identifiers to the one or more subscribers.