TornadoTornadoTwistedAsyncioNativePythonPython-Tornado V4 Storage & Playback API Reference for Realtime Apps

Go to Channel Groups


 

These docs are for PubNub 4.0 for Python-Tornado V4 which is our latest and greatest! For the docs of the older versions of the SDK, please check PubNub 3.0 for Python, PubNub 3.0 for Python-Tornado and PubNub 3.0 for Python-Twisted.

If you have questions about the PubNub for Python SDK, please contact us at support@pubnub.com.

Requires Storage & Playback add-on XRequires that the Storage & Playback add-on is enabled for your key. See this page on enabling add-on features on your keys:

http://www.pubnub.com/knowledge-base/discussion/644/how-do-i-enable-add-on-features-for-my-keys.
This function fetches historical messages of a channel.
PubNub Storage/Playback Service provides real-time access to an unlimited history for all messages published to PubNub. Stored messages are replicated across multiple availability zones in several geographical data center locations. Stored messages can be encrypted with AES-256 message encryption ensuring that they are not readable while stored on PubNub's network.
It is possible to control how messages are returned and in what order, for example you can:
  • Search for messages starting on the newest end of the timeline (default behavior - reverse = False)
  • Search for messages from the oldest end of the timeline by setting reverse to True.
  • Page through results by providing a start OR end time token.
  • Retrieve a slice of the time line by providing both a start AND end time token.
  • Limit the number of messages to a specific quantity using the count parameter.
 
Start & End parameter usage clarity:
If only the start parameter is specified (without end), you will receive messages that are older than and up to that start timetoken value.
If only the end parameter is specified (without start) you will receive messages that match that end timetoken value and newer.
Specifying values for both start and end parameters will return messages between those timetoken values (inclusive on the end value).
Keep in mind that you will still receive a maximum of 100 messages even if there are more messages that meet the timetoken values. Iterative calls to history adjusting the start timetoken is necessary to page through the full set of results if more than 100 messages meet the timetoken values.
To run History you can use the following method(s) in the Python-Tornado V4 SDK
  1. ParameterTypeRequiredDefaultsDescription
    channelStringYesSpecifies channel to return history messages from.
    reverseBooleanOptionalFalseSetting to True will traverse the time line in reverse starting with the oldest message first.
    include_timetokenBooleanOptionalFalseWhether event dates time tokens should be included in response or not.
    startIntOptionalTime token delimiting the start of time slice (exclusive) to pull messages from.
    endIntOptionalTime token delimiting the end of time slice (inclusive) to pull messages from.
    countIntOptionalSpecifies the number of historical messages to return.
Retrieve the last 100 messages on a channel:
envelope = yield pubnub.history()\
    .channel("history_channel")\
    .count(100)\
    .future()
The history() operation returns a PNHistoryResult which contains the following fields:
MethodTypeDescription
messages
List
List of messages of type PNHistoryItemResult. See PNHistoryItemResult for more details.
start_timetoken
Int
Start timetoken.
end_timetoken
Int
End timetoken.
MethodTypeDescription
timetoken
Int
Timetoken of the message.
entry
Object
Message.
  1. envelope = yield pubnub.history().channel("my_channel").count(3).reverse(True).future()
    {
        end_timetoken: 13406746729185766,
        start_timetoken: 13406746780720711,
        messages: [{
            crypto: None,
            entry: 'Pub1',
            timetoken: None
        },{
            crypto: None,
            entry: 'Pub2',
            timetoken: None
        },{
            crypto: None,
            entry: 'Pub2',
            timetoken: None
        }]
    }
  2. envelope = yield pubnub.history()\
        .channel("my_channel")\
        .start(13847168620721752)\
        .reverse(true)\
        .future()
    {
        end_timetoken: 13406746729185766,
        start_timetoken: 13406746780720711,
        messages: [{
            crypto: None,
            entry: 'Pub4',
            timetoken: None
        },{
            crypto: None,
            entry: 'Pub5',
            timetoken: None
        },{
            crypto: None,
            entry: 'Pub6',
            timetoken: None
        }]
    }
  3. envelope = yield pubnub.history()\
        .channel("my_channel")\
        .count(100)\
        .start(-1)\
        .end(13847168819178600)\
        .reverse(True)\
        .future()
    {
        end_timetoken: 13406746729185766,
        start_timetoken: 13406746780720711,
        messages: [{
            crypto: None,
            entry: 'Pub4',
            timetoken: None
        },{
            crypto: None,
            entry: 'Pub5',
            timetoken: None
        },{
            crypto: None,
            entry: 'Pub6',
            timetoken: None
        }]
    }
  4.  
    Usage!
    You can call the method by passing 0 or a valid time token as the argument.
    async def get_all_messages(start_tt):
        envelope = await pubnub.history()\
            .channel('history_channel')\
            .count(100)\
            .start(start_tt)\
            .future()
    
        msgs = envelope.result.messages
        start = envelope.result.start_timetoken
        end = envelope.result.end_timetoken
        count = len(msgs)
    
        if count > 0:
            print("%d" % count)
            print("start %d" % start)
            print("end %d" % end)
    
        if count == 100:
            await get_all_messages(start)
    
    if __name__ == '__main__':
        IOLoop.current().run_sync(lambda: get_all_messages(14759343456292767))
  5. envelope = yield pubnub.history()\
        .channel("my_channel")\
        .count(100)\
        .include_tometoken()
        .future()
Requires Storage & Playback add-on XRequires that the Storage & Playback add-on is enabled for your key. See this page on enabling add-on features on your keys:

http://www.pubnub.com/knowledge-base/discussion/644/how-do-i-enable-add-on-features-for-my-keys.
Removes the messages from the history of a specific channel.
 
There is a setting to accept delete from history requests for a key, which you must enable by checking the Enable Delete-From-History checkbox in the key settings for your key in the Administration Portal.

Requires Initialization with secret key.

To Delete Messages from History you can use the following method(s) in the Python-Tornado V4 SDK.
  1. ParameterTypeRequiredDefaultsDescription
    channelStringYesSpecifies channels to delete messages from.
    startIntOptionalTime token delimiting the start of time slice (inclusive) to delete messages from.
    endIntOptionalTime token delimiting the end of time slice (exclusive) to delete messages from.
envelope = yield pubnub.delete_messages()\
    .channel("my-ch")\
    .start(123)\
    .end(456)\
    .future()

  1. To delete a specific message, pass the publish timetoken (received from a successful publish) in the End parameter and timetoken +/- 1 in the Start parameter. e.g. if 15526611838554310 is the publish timetoken, pass 15526611838554309 in Start and 15526611838554310 in End parameters respectively as shown in the following code snippet.
    envelope = yield pubnub.delete_messages()\
        .channel("my-ch")\
        .start(15526611838554309)\
        .end(15526611838554310)\
        .future()

Go to Mobile Push