2010-09-16 04:18:01 +09:00
|
|
|
<?php
|
|
|
|
/*
|
|
|
|
* StatusNet - the distributed open-source microblogging tool
|
|
|
|
* Copyright (C) 2010 StatusNet, Inc.
|
|
|
|
*
|
|
|
|
* This program is free software: you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU Affero General Public License as published by
|
|
|
|
* the Free Software Foundation, either version 3 of the License, or
|
|
|
|
* (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU Affero General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU Affero General Public License
|
|
|
|
* along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/**
|
|
|
|
* Class for activity streams
|
|
|
|
*
|
|
|
|
* Includes faves, notices, and subscriptions.
|
|
|
|
*
|
|
|
|
* We extend atomusernoticefeed since it does some nice setup for us.
|
|
|
|
*
|
|
|
|
*/
|
|
|
|
class UserActivityStream extends AtomUserNoticeFeed
|
|
|
|
{
|
2011-01-03 08:22:12 +09:00
|
|
|
public $activities = array();
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
const OUTPUT_STRING = 1;
|
|
|
|
const OUTPUT_RAW = 2;
|
|
|
|
public $outputMode = self::OUTPUT_STRING;
|
|
|
|
|
|
|
|
/**
|
|
|
|
*
|
|
|
|
* @param User $user
|
|
|
|
* @param boolean $indent
|
|
|
|
* @param boolean $outputMode: UserActivityStream::OUTPUT_STRING to return a string,
|
|
|
|
* or UserActivityStream::OUTPUT_RAW to go to raw output.
|
|
|
|
* Raw output mode will attempt to stream, keeping less
|
|
|
|
* data in memory but will leave $this->activities incomplete.
|
|
|
|
*/
|
|
|
|
function __construct($user, $indent = true, $outputMode = UserActivityStream::OUTPUT_STRING)
|
2010-09-16 04:18:01 +09:00
|
|
|
{
|
|
|
|
parent::__construct($user, null, $indent);
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
$this->outputMode = $outputMode;
|
|
|
|
if ($this->outputMode == self::OUTPUT_STRING) {
|
|
|
|
// String buffering? Grab all the notices now.
|
|
|
|
$notices = $this->getNotices();
|
|
|
|
} elseif ($this->outputMode == self::OUTPUT_RAW) {
|
|
|
|
// Raw output... need to restructure from the stringer init.
|
|
|
|
$this->xw = new XMLWriter();
|
|
|
|
$this->xw->openURI('php://output');
|
|
|
|
if(is_null($indent)) {
|
|
|
|
$indent = common_config('site', 'indent');
|
|
|
|
}
|
|
|
|
$this->xw->setIndent($indent);
|
|
|
|
|
|
|
|
// We'll fetch notices later.
|
|
|
|
$notices = array();
|
|
|
|
} else {
|
|
|
|
throw new Exception('Invalid outputMode provided to ' . __METHOD__);
|
|
|
|
}
|
|
|
|
|
|
|
|
// Assume that everything but notices is feasible
|
|
|
|
// to pull at once and work with in memory...
|
2013-05-24 04:02:30 +09:00
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
$subscriptions = $this->getSubscriptions();
|
|
|
|
$subscribers = $this->getSubscribers();
|
|
|
|
$groups = $this->getGroups();
|
|
|
|
$faves = $this->getFaves();
|
|
|
|
|
|
|
|
$objs = array_merge($subscriptions, $subscribers, $groups, $faves, $notices);
|
|
|
|
|
|
|
|
// Sort by create date
|
|
|
|
|
|
|
|
usort($objs, 'UserActivityStream::compareObject');
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
// We'll keep these around for later, and interleave them into
|
|
|
|
// the output stream with the user's notices.
|
2010-09-16 04:18:01 +09:00
|
|
|
foreach ($objs as $obj) {
|
2013-05-24 04:02:30 +09:00
|
|
|
try {
|
|
|
|
$this->activities[] = $obj->asActivity();
|
|
|
|
} catch (Exception $e) {
|
|
|
|
// Continue
|
|
|
|
}
|
2011-01-03 08:22:12 +09:00
|
|
|
}
|
|
|
|
}
|
2011-01-29 08:33:13 +09:00
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
/**
|
|
|
|
* Interleave the pre-sorted subs/groups/faves with the user's
|
|
|
|
* notices, all in reverse chron order.
|
|
|
|
*/
|
2011-01-03 08:22:12 +09:00
|
|
|
function renderEntries()
|
|
|
|
{
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
$end = time() + 1;
|
2011-01-03 08:22:12 +09:00
|
|
|
foreach ($this->activities as $act) {
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
$start = $act->time;
|
|
|
|
|
|
|
|
if ($this->outputMode == self::OUTPUT_RAW && $start != $end) {
|
|
|
|
// In raw mode, we haven't pre-fetched notices.
|
|
|
|
// Grab the chunks of notices between other activities.
|
|
|
|
$notices = $this->getNoticesBetween($start, $end);
|
|
|
|
foreach ($notices as $noticeAct) {
|
2013-05-24 04:02:30 +09:00
|
|
|
try {
|
|
|
|
$nact = $noticeAct->asActivity();
|
|
|
|
$nact->outputTo($this, false, false);
|
|
|
|
} catch (Exception $e) {
|
|
|
|
// Continue
|
|
|
|
}
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
// Only show the author sub-element if it's different from default user
|
2011-01-03 08:22:12 +09:00
|
|
|
$act->outputTo($this, false, ($act->actor->id != $this->user->uri));
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
|
|
|
|
$end = $start;
|
|
|
|
}
|
|
|
|
|
|
|
|
if ($this->outputMode == self::OUTPUT_RAW) {
|
|
|
|
// Grab anything after the last pre-sorted activity.
|
|
|
|
$notices = $this->getNoticesBetween(0, $end);
|
|
|
|
foreach ($notices as $noticeAct) {
|
2013-05-24 04:02:30 +09:00
|
|
|
try {
|
|
|
|
$nact = $noticeAct->asActivity();
|
|
|
|
$nact->outputTo($this, false, false);
|
|
|
|
} catch (Exception $e) {
|
|
|
|
// Continue
|
|
|
|
}
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
}
|
2010-09-16 04:18:01 +09:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
function compareObject($a, $b)
|
|
|
|
{
|
|
|
|
$ac = strtotime((empty($a->created)) ? $a->modified : $a->created);
|
|
|
|
$bc = strtotime((empty($b->created)) ? $b->modified : $b->created);
|
|
|
|
|
|
|
|
return (($ac == $bc) ? 0 : (($ac < $bc) ? 1 : -1));
|
|
|
|
}
|
|
|
|
|
|
|
|
function getSubscriptions()
|
|
|
|
{
|
|
|
|
$subs = array();
|
|
|
|
|
|
|
|
$sub = new Subscription();
|
|
|
|
|
|
|
|
$sub->subscriber = $this->user->id;
|
|
|
|
|
|
|
|
if ($sub->find()) {
|
|
|
|
while ($sub->fetch()) {
|
|
|
|
if ($sub->subscribed != $this->user->id) {
|
|
|
|
$subs[] = clone($sub);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $subs;
|
|
|
|
}
|
|
|
|
|
|
|
|
function getSubscribers()
|
|
|
|
{
|
|
|
|
$subs = array();
|
|
|
|
|
|
|
|
$sub = new Subscription();
|
|
|
|
|
|
|
|
$sub->subscribed = $this->user->id;
|
|
|
|
|
|
|
|
if ($sub->find()) {
|
|
|
|
while ($sub->fetch()) {
|
|
|
|
if ($sub->subscriber != $this->user->id) {
|
|
|
|
$subs[] = clone($sub);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $subs;
|
|
|
|
}
|
|
|
|
|
|
|
|
function getFaves()
|
|
|
|
{
|
|
|
|
$faves = array();
|
|
|
|
|
|
|
|
$fave = new Fave();
|
|
|
|
|
|
|
|
$fave->user_id = $this->user->id;
|
|
|
|
|
|
|
|
if ($fave->find()) {
|
|
|
|
while ($fave->fetch()) {
|
|
|
|
$faves[] = clone($fave);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $faves;
|
|
|
|
}
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
/**
|
|
|
|
*
|
|
|
|
* @param int $start unix timestamp for earliest
|
|
|
|
* @param int $end unix timestamp for latest
|
|
|
|
* @return array of Notice objects
|
|
|
|
*/
|
|
|
|
function getNoticesBetween($start=0, $end=0)
|
2010-09-16 04:18:01 +09:00
|
|
|
{
|
|
|
|
$notices = array();
|
|
|
|
|
|
|
|
$notice = new Notice();
|
|
|
|
|
|
|
|
$notice->profile_id = $this->user->id;
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
if ($start) {
|
|
|
|
$tsstart = common_sql_date($start);
|
|
|
|
$notice->whereAdd("created >= '$tsstart'");
|
|
|
|
}
|
|
|
|
if ($end) {
|
|
|
|
$tsend = common_sql_date($end);
|
|
|
|
$notice->whereAdd("created < '$tsend'");
|
|
|
|
}
|
|
|
|
|
|
|
|
$notice->orderBy('created DESC');
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
if ($notice->find()) {
|
|
|
|
while ($notice->fetch()) {
|
|
|
|
$notices[] = clone($notice);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $notices;
|
|
|
|
}
|
|
|
|
|
Scalability work on user backup stream generation.
UserActivityStream -- used to create a full activity stream including subscriptions, favorites, notices, etc -- normally buffers everything into memory at once. This is infeasible for accounts with long histories of serious usage; it can take tens of seconds just to pull all records from the database, and working with them all in memory is very likely to hit resource limits.
This commit adds an alternate mode for this class which avoids pulling notices until during the actual output. Instead of pre-sorting and buffering all the notices, empty spaces between the other activities are filled in with notices as we're making output. This means more smaller queries spread out during operations, and less stuff kept in memory.
Callers (backupaccount action, and backupuser.php) which can stream their output pass an $outputMode param of UserActivityStream::OUTPUT_RAW, and during getString() it'll send straight to output as well as slurping the notices in this extra funky fashion.
Other callers will let it default to the OUTPUT_STRING mode, which keeps the previous behavior.
There should be a better way to do this, swapping out the stringer output for raw output more consitently.
2011-02-26 04:04:57 +09:00
|
|
|
function getNotices()
|
|
|
|
{
|
|
|
|
return $this->getNoticesBetween();
|
|
|
|
}
|
|
|
|
|
2010-09-16 04:18:01 +09:00
|
|
|
function getGroups()
|
|
|
|
{
|
|
|
|
$groups = array();
|
|
|
|
|
|
|
|
$gm = new Group_member();
|
|
|
|
|
|
|
|
$gm->profile_id = $this->user->id;
|
|
|
|
|
|
|
|
if ($gm->find()) {
|
|
|
|
while ($gm->fetch()) {
|
|
|
|
$groups[] = clone($gm);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return $groups;
|
|
|
|
}
|
|
|
|
}
|