IPP Mail Archive: RE: IPP> Duplicate ippget events

IPP Mail Archive: RE: IPP> Duplicate ippget events

RE: IPP> Duplicate ippget events

From: McDonald, Ira (imcdonald@sharplabs.com)
Date: Sat Jul 28 2001 - 17:53:07 EDT

  • Next message: gajt@bellsouth.com: "IPP> Saw your site Saw your site (9064)"

    Hi Marty and Michael,

    The operation attribute "notify-subscription-id" (OPTIONAL) in
    Get-Notifications is SINGLE-VALUED. If you want to add an
    (OPTIONAL) "notify-sequence-number" operation attribute, then
    the accompanying "notify-subscription-id" MUST be specified,
    right?

    Then this all hangs together nicely and avoids duplicate
    harvesting of events which have been SUCCESSFULLY received
    by the IPP Notification Receiver (remember the connection
    might have broken just as the previous events were sent).

    Cheers,
    - Ira McDonald

    -----Original Message-----
    From: Marty Joel [mailto:mjoel@netreon.com]
    Sent: Friday, July 27, 2001 5:42 PM
    To: ipp@pwg.org
    Subject: Re: IPP> Duplicate ippget events

    Hi Michael,

    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).

    Marty

    Michael Sweet <mike@easysw.com>@pwg.org on 07/27/2001 12:43:56 PM

    Sent by: owner-ipp@pwg.org

    To: Marty Joel <mjoel@netreon.com>
    cc: ipp@pwg.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...

    Thoughts?

    --
    ______________________________________________________________________
    Michael Sweet, Easy Software Products                  mike@easysw.com
    Printing Software for UNIX                       http://www.easysw.com
    



    This archive was generated by hypermail 2b29 : Sat Jul 28 2001 - 18:01:46 EDT