ProPeler
Home
Console
Upload
information
Create File
Create Folder
About
Tools
:
/
opt
/
cpanel-ccs
/
calendarserver
/
push
/
Filename :
util.pyc
back
Copy
� �t�ac @ s� d d l m Z d d l m Z m Z m Z d d l Z d d l m Z d d l Z d � Z d � Z d � Z d � Z d � Z d e f d � � YZ d e f d � � YZ d S( i����( t Logger( t getPasswordFromKeychaint KeychainAccessErrort KeychainPasswordNotFoundN( t cryptoc C s� t t d � r� | j r� t j j | j � } | r] t d j d | d | j d | � � � n | j s� t | j � } | | _ n | j s� t d j d | � � � q� q�t d j d | � � � n� t j j | j � s� t d j d | d | j � � � n | j s t | j � } | | _ n | j sDt d j d | � � � n | j s�y t | � } | | _ Wq�t k ryq�t k r�t d j d | � � � q�Xn d S( s+ Given the APNS protocol config, extract the APN topic. @param accountName: account name @type accountName: L{str} @param protocol: APNS protocol name @type protocol: L{str} @param protoConfig: APNS specific config @type protoConfig: L{dict} @raise: ValueError t __SecureTransport__sD The {proto} APNS Keychain Identity ({cert}) cannot be used: {reason}t protot certt reasons! Cannot extract {proto} APNS topics) No {proto} APNS Keychain Identity was sets0 The {proto} APNS certificate ({cert}) is missings5 Cannot retrieve {proto} APNS passphrase from keychainN( t hasattrt OpenSSLt KeychainIdentityR t check_keychain_identityt ValueErrort formatt Topict getAPNTopicFromIdentityt ost patht existst CertificatePatht getAPNTopicFromCertificatet PassphraseR R R ( t protocolt accountNamet protoConfigt errort topict passphrase( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyt getAPNTopicFromConfig sD c C s: t | � � } | j � } Wd QXt t j t j | � � S( s( Given the path to a certificate, extract the UID value portion of the subject, which in this context is used for the associated APN topic. @param certPath: file path of the certificate @type certPath: C{str} @return: C{str} topic, or empty string if value is not found N( t opent readt getAPNTopicFromX509R t load_certificatet FILETYPE_PEM( t certPatht ft certData( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyR ` s c C s t t j d | � � S( s- Given a keychain identity certificate, extract the UID value portion of the subject, which in this context is used for the associated APN topic. @param identity: keychain identity to lookup @type identity: C{str} @return: C{str} topic, or empty string if value is not found N( R R R! t None( t identity( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyR o s c C sC | j � } | j � } x$ | D] \ } } | d k r | Sq Wd S( s Given an L{X509} certificate, extract the UID value portion of the subject, which in this context is used for the associated APN topic. @param x509: the certificate @type x509: L{X509} @return: C{str} topic, or empty string if value is not found t UIDt ( t get_subjectt get_components( t x509t subjectt componentst namet value( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyR | s c C s4 | s t Sy | j d � Wn t k r/ t SXt S( sN Return True if token is in hex and is not empty, False otherwise t hex( t Falset decodet TypeErrort True( t token( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyt validToken� s t TokenHistoryc B s, e Z d Z d d � Z d � Z d � Z RS( s� Manages a queue of tokens and corresponding identifiers. Queue is always kept below maxSize in length (older entries removed as needed). i� c C s | | _ d | _ g | _ d S( s� @param maxSize: How large the history is allowed to grow. Once this size is reached, older entries are pruned as needed. @type maxSize: C{int} i N( t maxSizet identifiert history( t selfR9 ( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyt __init__� s c C s= | j d 7_ | j j | j | f � | j | j 4| j S( s� Add a token to the history, and return the new identifier associated with this token. Identifiers begin at 1 and increase each time this is called. If the number of items in the history exceeds maxSize, older entries are removed to get the size down to maxSize. @param token: The token to store @type token: C{str} @returns: the message identifier associated with this token, C{int} i ( R: R; t appendR9 ( R< R6 ( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyt add� s c C sD x= t | j � D], \ } \ } } | | k r | j | =| Sq Wd S( s� Look for the token associated with the identifier. Remove the identifier-token pair from the history and return the token. Return None if the identifier is not found in the history. @param identifier: The identifier to look up @type identifier: C{int} @returns: the token associated with this message identifier, C{str}, or None if not found N( t enumerateR; R& ( R< R: t indext idR6 ( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyt extractIdentifier� s " ( t __name__t __module__t __doc__R= R? RC ( ( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyR8 � s t PushSchedulerc B s> e Z d Z e � Z d d � Z d � Z d � Z d � Z RS( s; Allows staggered scheduling of push notifications i c C s( i | _ | | _ | | _ | | _ d S( s� @param callback: The method to call when it's time to send a push @type callback: callable @param staggerSeconds: The number of seconds to stagger between each push @type staggerSeconds: integer N( t outstandingt reactort callbackt staggerSeconds( R< RI RJ RK ( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyR= � s c C s� d } x� | D]� } | | f } | | j k rG | j j d d | �q | j j | | j | | | | � | j | <| j j d d | d | �| | j 7} q Wd S( s� Schedules a batch of notifications for the given tokens, staggered with self.staggerSeconds between each one. Duplicates are ignored, so if a token/key pair is already scheduled and not yet sent, a new one will not be scheduled for that pair. @param tokens: The device tokens to schedule notifications for @type tokens: List of C{str} @param key: The key to use for this batch of notifications @type key: C{str} @param dataChangedTimestamp: Timestamp (epoch seconds) for the data change which triggered this notification @type key: C{int} g s/ PushScheduler already has this scheduled: {key}t keys0 PushScheduler scheduled: {key} in {time:.0f} sect timeN( RH t logt debugRI t callLatert sendRK ( R< t tokensRL t dataChangedTimestampt priorityt scheduleTimeR6 t internalKey( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyt schedule� s c C sH | j j d d | d | d | �| j | | f =| j | | | | � S( s� This method is what actually gets scheduled. Its job is to remove its corresponding entry from the outstanding dict and call the callback. @param token: The device token to send a notification to @type token: C{str} @param key: The notification key @type key: C{str} @param dataChangedTimestamp: Timestamp (epoch seconds) for the data change which triggered this notification @type key: C{int} s, PushScheduler fired for {token} {key} {time}R6 RL RM ( RN RO RH RJ ( R< R6 RL RS RT ( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyRQ s "c C sP xI | j j � D]8 \ \ } } } | j j d d | d | �| j � q Wd S( s6 Cancel all outstanding delayed calls s& PushScheduler cancelling {token} {key}R6 RL N( RH t iteritemsRN RO t cancel( R< R6 RL t delayed( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyt stop s " ( RD RE RF R RN R= RW RQ R[ ( ( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyRG � s ! ( t twext.python.logR t twistedcaldav.utilR R R R R R R R R R R7 t objectR8 RG ( ( ( s+ /opt/cpanel-ccs/calendarserver/push/util.pyt <module> s D 2