1. 31 Jan, 2011 1 commit
  2. 27 Nov, 2010 2 commits
  3. 08 Oct, 2010 1 commit
  4. 19 Sep, 2010 1 commit
  5. 07 Sep, 2010 1 commit
  6. 02 Aug, 2010 1 commit
  7. 04 Mar, 2010 1 commit
  8. 25 Feb, 2010 2 commits
  9. 09 Feb, 2010 1 commit
  10. 22 Jan, 2010 4 commits
    • Craig Andrews's avatar
      Will re-enable anything queueing after 0.9.x merge · 78eb9c78
      Craig Andrews authored
      Revert "Any object (not just Notice's) can be queued"
      
      This reverts commit 77ea02ca.
      78eb9c78
    • Brion Vibber's avatar
      XMPP queued output & initial retooling of DB queue manager to support non-Notice objects. · c7507e7e
      Brion Vibber authored
      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
      c7507e7e
    • Brion Vibber's avatar
      XMPP queued output & initial retooling of DB queue manager to support non-Notice objects. · 0e852def
      Brion Vibber authored
      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.
      0e852def
    • Brion Vibber's avatar
      XMPP queued output & initial retooling of DB queue manager to support non-Notice objects. · 26fdf0c9
      Brion Vibber authored
      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.
      26fdf0c9
  11. 21 Jan, 2010 1 commit
  12. 06 Jan, 2010 1 commit
  13. 21 Oct, 2009 1 commit
  14. 20 Oct, 2009 1 commit
  15. 08 Oct, 2009 1 commit
    • Evan Prodromou's avatar
      Revert "Open tags should have closing tags" · a6d4adc3
      Evan Prodromou authored
      This reverts commit aeca8807.
      
      We specifically DON'T have closing tags so we don't get errors with
      whitespace after the closing tag.
      
      I realize this is less of an issue with scripts, but we should still
      not use closing tags.
      a6d4adc3
  16. 05 Oct, 2009 1 commit
  17. 25 Aug, 2009 2 commits
  18. 22 Jun, 2009 2 commits
  19. 20 Jun, 2009 3 commits
  20. 16 Feb, 2009 1 commit
  21. 12 Feb, 2009 1 commit
  22. 23 Dec, 2008 4 commits
    • Evan Prodromou's avatar
      move opening brace of class declaration to next line · b264c03d
      Evan Prodromou authored
      Another gigantor PEAR coding standards patch. Here, I've moved the
      opening curly bracket on a class statement to the following line.
      
      darcs-hash:20081223194923-84dde-77a93de314caadbcb5b70bf346a4648be77a864e.gz
      b264c03d
    • Evan Prodromou's avatar
      change function headers to K&R style · 04ef1ba8
      Evan Prodromou authored
      Another huge change, for PEAR code standards compliance. Function
      headers have to be in K&R style (opening brace on its own line),
      instead of having the opening brace on the same line as the function
      and parameters. So, a little perl magic found all the function
      definitions and move the opening brace to the next line (properly
      indented... usually).
      
      darcs-hash:20081223193323-84dde-a28e36ecc66672c783c2842d12fc11043c13ab28.gz
      04ef1ba8
    • Evan Prodromou's avatar
      replace NULL with null · eb2f9c98
      Evan Prodromou authored
      Another global search-and-replace update. Here, I've replaced the PHP
      keyword 'NULL' with its lowercase version. This is another PEAR code
      standards change.
      
      darcs-hash:20081223192129-84dde-4a0182e0ec16a01ad88745ad3e08f7cb501aee0b.gz
      eb2f9c98
    • Evan Prodromou's avatar
      replace all tabs with four spaces · edbc0c66
      Evan Prodromou authored
      The PEAR coding standards decree: no tabs, but indent by four spaces.
      I've done a global search-and-replace on all tabs, replacing them by
      four spaces. This is a huge change, but it will go a long way to
      getting us towards phpcs-compliance. And that means better code
      readability, and that means more participation.
      
      darcs-hash:20081223191907-84dde-21e8efe210e6d5d54e935a22d0cee5c7bbfc007d.gz
      edbc0c66
  23. 04 Sep, 2008 1 commit
  24. 31 Aug, 2008 2 commits
  25. 30 Aug, 2008 2 commits
  26. 28 Aug, 2008 1 commit