Changeset 291:bd9013d79121

Show
Ignore:
Timestamp:
11/01/12 23:09:49 (4 months ago)
Author:
Menno Smits <menno@…>
Branch:
default
Message:

clarified documentation relating to message identifiers

Files:
1 modified

Legend:

Unmodified
Added
Removed
  • doc/src/index.rst

    r275 r291  
    7171Message Identifiers 
    7272~~~~~~~~~~~~~~~~~~~ 
    73 There are two ways to refer to messages using the IMAP protocol.  
     73There are two ways to refer to messages using the IMAP protocol. 
    7474 
    7575One way is by message sequence number where the messages in a mailbox 
     
    7979 
    8080A more convenient approach is Unique Identifiers (UIDs). Unique 
    81 Identifiers are integer assigned to each message by the IMAP server 
     81Identifiers are integers assigned to each message by the IMAP server 
    8282that will persist across sessions. They do not change when folders are 
    8383expunged. 
     
    8989 
    9090Any method that accepts message ids takes either a sequence containing 
    91 message ids (eg. ``[1,2,3]``) or a single message id integer. Whether 
    92 these are interpreted as message sequence numbers or UIDs depends on 
    93 the *use_uid* argument used when the IMAPClient instance is created 
    94 and the *use_uid* attribute. The *use_uid* attribute can be used to 
    95 change the message id type between calls to the server. 
     91message ids (eg. ``[1,2,3]``), or a single message id integer, or a 
     92string representing sets and ranges of messages as supported by the 
     93IMAP protocol (e.g. ``'50-65'``, ``'2:*'`` or 
     94``'2,4:7,9,12:*'``). Whether these are interpreted as message sequence 
     95numbers or UIDs depends on the *use_uid* argument passed when an 
     96IMAPClient instance is created and the *use_uid* attribute. The 
     97*use_uid* attribute can be used to change the message id type between 
     98calls to the server. 
    9699 
    97100Message Flags