o

y)�]��@sdZd
Z
dd�ZdS)z/Helpers for reliable persistent message queues.�
cCshd
}|��}|
|kr|�
�
|
|}n|
||��kr d}t}n|��|
|}|�|�

|�|
�

|S)aOur peer has told us what it expects our next message's sequence to be.

    Call this with the message store and sequence number that the peer
    wants next; this will do various things based on what *this* side
    has in its outbound queue store.

    1. The peer expects a sequence greater than what we last
       sent. This is the common case and generally it should be
       expecting last_sent_sequence+len(messages_sent)+1.

    2. The peer expects a sequence number our side has already sent,
       and we no longer have that message. In this case, just send
       *all* messages we have, including the previous generation,
       starting at the sequence number the peer expects (meaning that
       messages have probably been lost).

    3. The peer expects a sequence number we already sent, and we
       still have that message cached. In this case, we send starting
       from that message.

    If the next expected sequence from the server refers to a message
    older than we have, then L{ANCIENT} will be returned.
    N�)�get_sequence�delete_old_messages�get_pending_offset�ANCIENT�set_pending_offset�set_sequence)�store�
next_expected�ret�old_sequence�pending_offset�r�7/usr/lib/python3/dist-packages/landscape/lib/message.py�got_next_expecteds 







�
�



rN)�__doc__rrrrrr�<module>
s