[ Index ] |
PHP Cross Reference of Phabricator |
[Source view] [Print] [Project Stats]
(no description)
File Size: | 279 lines (8 kb) |
Included or required: | 0 times |
Referenced: | 0 times |
Includes or requires: | 0 files |
setMailTags(array $mail_tags) X-Ref |
No description |
getMailTags() X-Ref |
No description |
setNotifyAuthor($notify_author) X-Ref |
No description |
getNotifyAuthor() X-Ref |
No description |
setRelatedPHIDs(array $phids) X-Ref |
No description |
setSubscribedPHIDs(array $phids) X-Ref |
No description |
setPrimaryObjectPHID($phid) X-Ref |
No description |
setStoryType($story_type) X-Ref |
No description |
setStoryData(array $data) X-Ref |
No description |
setStoryTime($time) X-Ref |
No description |
setStoryAuthorPHID($phid) X-Ref |
No description |
setMailRecipientPHIDs(array $phids) X-Ref |
No description |
publish() X-Ref |
No description |
insertNotifications($chrono_key, array $subscribed_phids) X-Ref |
No description |
sendNotification($chrono_key, array $subscribed_phids) X-Ref |
No description |
filterSubscribedPHIDs(array $phids) X-Ref |
Remove PHIDs who should not receive notifications from a subscriber list. param: list<phid> List of potential subscribers. return: list<phid> List of actual subscribers. |
generateChronologicalKey() X-Ref |
We generate a unique chronological key for each story type because we want to be able to page through the stream with a cursor (i.e., select stories after ID = X) so we can efficiently perform filtering after selecting data, and multiple stories with the same ID make this cumbersome without putting a bunch of logic in the client. We could use the primary key, but that would prevent publishing stories which happened in the past. Since it's potentially useful to do that (e.g., if you're importing another data source) build a unique key for each story which has chronological ordering. return: string A unique, time-ordered key which identifies the story. |
Generated: Sun Nov 30 09:20:46 2014 | Cross-referenced by PHPXref 0.7.1 |