Age | Commit message (Collapse) | Author |
|
I made a bad merge on Jan 10th from master to 0.9.x. This lost a number
of memcache enhancements made on the 0.9.x branch. I've been able to
re-do the manual merge, and this represents the changes. Most of them
are related to caching on insert.
|
|
|
|
|
|
|
|
seeked, MobileProfile plugin should be used.
|
|
|
|
(under author's photo) b) supplemental notice content and options will
start right under notice text.
|
|
|
|
few bugs in WebKit)
|
|
|
|
|
|
Also avoids the conflict with the URL fragment on the conversation page.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
fails to ask for user permission, causing us quite a bit of difficulty."
This reverts commit 749b8b5b8ca4d1c39d350879aadddbdb9d8b71d5.
|
|
|
|
|
|
|
|
|
|
|
|
non-English word order)
(Note the .po files will have to be added manually for now as we haven't set TranslateWiki up for plugins I think)
|
|
server response (if any on failure) to go to log instead of stdout.
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
state. This code's a little rough and tumble; any breakage halts JS execution and leaves the spinner going and no message submitted.
|
|
$config['db']['log_queries'] = true; // all
$config['db']['log_slow_queries'] = 10; // queries taking > 10 seconds
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 906450e2f5b78a1c6f2dec2e21b9b5841df210f4.
1) It was a quick debug hack 2) it doesn't meet the requirements
for changing extlib/ libraries
|
|
|
|
|