I agree, but that means the client will have to send a list of
notify-subscription-id / notify-sequence-number pairs (although I realize
there would usually only be one).
Michael Sweet <email@example.com>@pwg.org on 07/27/2001 12:43:56 PM
Sent by: firstname.lastname@example.org
Subject: Re: IPP> Duplicate ippget events
Marty Joel wrote:
> Hi Michael,
> I agree with everything you've said.
> Actually, notify-sequence-number is what should be used by the client to
> ignore duplicates. For each subscription that matches its
> Get-Notifications (usually only 1 subscription), it needs to know that
> subscription ID and the last notify-sequence-number it received. That
> requires very little work on the part of the client.
Hmmm, from an implementation standpoint, it would be better if the
client could send the last sequence number is has received to the
server, so the server would only have to send events whose sequence
number is > the one provided. E.g., a client sends a server the
"notify-sequence-number" attribute in the Get-Notifications request,
and the server responds only with those events that have a higher
sequence number. This would also reduce the bandwidth used...
-- ______________________________________________________________________ Michael Sweet, Easy Software Products email@example.com Printing Software for UNIX http://www.easysw.com
This archive was generated by hypermail 2b29 : Fri Jul 27 2001 - 17:46:30 EDT