On 8/19/11 12:12 PM, "Justin Karneges" <[email protected]> wrote:
> In the context of PEP, it would just be a matter of putting this same type of > position spec into the subscription request, and then each remote node would > reply with all items since that time (or just the one item only if it has > changed, I think PEP is always singleton?). There's no reason PEP is always a singleton. If the publisher wants singleton, she uses id='current'. > Indeed. In my case I consider a time-based query to be inclusive, so as to > not miss updates occuring within the same second. In the rare case you pick > up the same item again, it's harmless. I'd go a little further, and suggest that the publishing server should back up enough time to account for clock skew, and republish everything from that earlier time. 5-10m should do it, as long as there aren't a lot of items. -- Joe Hildebrand
