summaryrefslogtreecommitdiff
path: root/lib
AgeCommit message (Collapse)Author
2010-01-25Fix presence notification on XMPP thread (now foreground, not background)Brion Vibber
2010-01-25Fix presence notification on XMPP thread (now foreground, not background)Brion Vibber
2010-01-25- Had to remove checking read vs. read-write in OAuth authenticated methodsZach Copley
- Will now pick up source attr from OAuth app
2010-01-24Add Start/EndSetApiUser events when setting API user via OAuthZach Copley
2010-01-24Check for read vs. read-write access on OAuth authenticated API mehtods.Zach Copley
2010-01-24Revoke access token UIZach Copley
2010-01-24Fix approval date and label on apps listZach Copley
2010-01-24Make sure applications are really looked up by consumer keyZach Copley
2010-01-24Rework application registration workflow to be more privateZach Copley
2010-01-24OAuth 1.0 working nowZach Copley
2010-01-24Updated markup for application edit form; image, radiosSarven Capadisli
2010-01-24A little minimizationSarven Capadisli
2010-01-24Added vcard and photo classesSarven Capadisli
2010-01-24Moved application image inside the anchorSarven Capadisli
2010-01-24Added missing end tagSarven Capadisli
2010-01-24Make API auth handle OAuth requests w/access tokensZach Copley
2010-01-24Fixed tabbingSarven Capadisli
2010-01-24Updated class for application listSarven Capadisli
2010-01-24Updated markup for application edit form submitsSarven Capadisli
2010-01-24Better detial in connected OAuth applications listZach Copley
2010-01-24Exchanging authorized request tokens for access tokens workingZach Copley
2010-01-24Workflow for request tokens and authorizing request tokensZach Copley
2010-01-24Action for issuing a request tokenZach Copley
2010-01-24Stubs for API OAuth token exchange stuffZach Copley
2010-01-24Add icons/icon upload to Oauth appsZach Copley
2010-01-24Workflow for registering new OAuth apps pretty much done.Zach Copley
2010-01-24Reorganized the OAuth app URLs and more work on the register app workflowZach Copley
2010-01-24Started work on interface for displaying connected OAuth appsZach Copley
2010-01-24Use new StatusNetwork->serverName() to get full domain for wildcard config ↵Brion Vibber
until we rebuild queues to be based on nicknames. Fixes live bug with new *.status.net sites breaking queuedaemon.php
2010-01-24defaults for nickname and wildcardEvan Prodromou
2010-01-24Use new StatusNetwork->serverName() to get full domain for wildcard config ↵Brion Vibber
until we rebuild queues to be based on nicknames. Fixes live bug with new *.status.net sites breaking queuedaemon.php
2010-01-24defaults for nickname and wildcardEvan Prodromou
2010-01-24Removed mobile stylesheet from core output. If Mobile support isSarven Capadisli
seeked, MobileProfile plugin should be used.
2010-01-24Updated path to farbtastic stylesheetSarven Capadisli
2010-01-24Event hooks for before and after site_noticeSarven Capadisli
2010-01-22Fix unqueuemanager for updated QueueHandler interfaceBrion Vibber
2010-01-22Fix unqueuemanager for updated QueueHandler interfaceBrion Vibber
2010-01-22Fix for stuck queue messages: wrap processing in stomp transactions so our ↵Brion Vibber
lack of an ACK if PHP dies actually triggers redelivery. Previously, messages once delivered would just get stuck in the queue seemingly forever if they never got ACKed. Note this could lead to partial duplication, for instance if the OMB or Twitter queue handlers die after 1/2 of the outgoing sends. Recommendations: * catch exceptions more aggressively within queue handlers (so only PHP fatal errors are likely to kill in the middle) * for processing that involves sending to multiple clients, consider a second queue similar to the XMPP output, eg for OMB: - first queue gets delivery list and builds message data, enqueueing it for each target address - second queue can handle each individual outgoing message (and attempt redelivery etc separately) This would also protect better against a recurring error preventing delivery in the second part, and could spread out any slow sends over multiple threads.
2010-01-22XMPP queued output & initial retooling of DB queue manager to support ↵Brion Vibber
non-Notice objects. Queue handlers for XMPP individual & firehose output now send their XML stanzas to another output queue instead of connecting directly to the chat server. This lets us have as many general processing threads as we need, while all actual XMPP input and output go through a single daemon with a single connection open. This avoids problems with multiple connected resources: * multiple windows shown in some chat clients (psi, gajim, kopete) * extra load on server * incoming message delivery forwarding issues Database changes: * queue_item drops 'notice_id' in favor of a 'frame' blob. This is based on Craig Andrews' work branch to generalize queues to take any object, but conservatively leaving out the serialization for now. Table updater (preserves any existing queued items) in db/rc3to09.sql Code changes to watch out for: * Queue handlers should now define a handle() method instead of handle_notice() * QueueDaemon and XmppDaemon now share common i/o (IoMaster) and respawning thread management (RespawningDaemon) infrastructure. * The polling XmppConfirmManager has been dropped, as the message is queued directly when saving IM settings. * Enable $config['queue']['debug_memory'] to output current memory usage at each run through the event loop to watch for memory leaks To do: * Adapt XMPP i/o to component connection mode for multi-site support. * XMPP input can also be broken out to a queue, which would allow the actual notice save etc to be handled by general queue threads. * Make sure there are no problems with simply pushing serialized Notice objects to queues. * Find a way to improve interactive performance of the database-backed queue handler; polling is pretty painful to XMPP. * Possibly redo the way QueueHandlers are injected into a QueueManager. The grouping used to split out the XMPP output queue is a bit awkward. Conflicts: scripts/xmppdaemon.php
2010-01-22Fix for stuck queue messages: wrap processing in stomp transactions so our ↵Brion Vibber
lack of an ACK if PHP dies actually triggers redelivery. Previously, messages once delivered would just get stuck in the queue seemingly forever if they never got ACKed. Note this could lead to partial duplication, for instance if the OMB or Twitter queue handlers die after 1/2 of the outgoing sends. Recommendations: * catch exceptions more aggressively within queue handlers (so only PHP fatal errors are likely to kill in the middle) * for processing that involves sending to multiple clients, consider a second queue similar to the XMPP output, eg for OMB: - first queue gets delivery list and builds message data, enqueueing it for each target address - second queue can handle each individual outgoing message (and attempt redelivery etc separately) This would also protect better against a recurring error preventing delivery in the second part, and could spread out any slow sends over multiple threads.
2010-01-21XMPP queued output & initial retooling of DB queue manager to support ↵Brion Vibber
non-Notice objects. Queue handlers for XMPP individual & firehose output now send their XML stanzas to another output queue instead of connecting directly to the chat server. This lets us have as many general processing threads as we need, while all actual XMPP input and output go through a single daemon with a single connection open. This avoids problems with multiple connected resources: * multiple windows shown in some chat clients (psi, gajim, kopete) * extra load on server * incoming message delivery forwarding issues Database changes: * queue_item drops 'notice_id' in favor of a 'frame' blob. This is based on Craig Andrews' work branch to generalize queues to take any object, but conservatively leaving out the serialization for now. Table updater (preserves any existing queued items) in db/rc3to09.sql Code changes to watch out for: * Queue handlers should now define a handle() method instead of handle_notice() * QueueDaemon and XmppDaemon now share common i/o (IoMaster) and respawning thread management (RespawningDaemon) infrastructure. * The polling XmppConfirmManager has been dropped, as the message is queued directly when saving IM settings. * Enable $config['queue']['debug_memory'] to output current memory usage at each run through the event loop to watch for memory leaks To do: * Adapt XMPP i/o to component connection mode for multi-site support. * XMPP input can also be broken out to a queue, which would allow the actual notice save etc to be handled by general queue threads. * Make sure there are no problems with simply pushing serialized Notice objects to queues. * Find a way to improve interactive performance of the database-backed queue handler; polling is pretty painful to XMPP. * Possibly redo the way QueueHandlers are injected into a QueueManager. The grouping used to split out the XMPP output queue is a bit awkward.
2010-01-21Option to log slow db queries or all db queriesBrion Vibber
$config['db']['log_queries'] = true; // all $config['db']['log_slow_queries'] = 10; // queries taking > 10 seconds
2010-01-19allow all rights reserved, private dataEvan Prodromou
2010-01-18add event for showing content license in actionEvan Prodromou
2010-01-16Merge branch 'master' of git@gitorious.org:statusnet/mainlineEvan Prodromou
2010-01-16change rc3 to beta3Evan Prodromou
2010-01-15--xmpp-only hack for queuedaemon.php to run separate queue daemon with only ↵Brion Vibber
xmpp threads
2010-01-14fix for --skip-xmpp hack -- forgot to do it on the ping & confirm handlersBrion Vibber
2010-01-14temporary --skip-xmpp flag on queuedaemon.php, allows to run queue daemons ↵Brion Vibber
but skip subscription to xmpp-based queues (still working on making these behave gracefully when server is down)
2010-01-14Keep handler registration per-site to fix queue registration in mixed config ↵Brion Vibber
environment