GitHost.io will be shut down on June 1, 2019. At that point this instance will be unreachable and all data will be irrevocably deleted. More details at https://about.gitlab.com/gitlab-hosted/#githost-is-shutting-down-on-june-1st-2019

  1. 27 Jan, 2010 1 commit
  2. 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
  3. 21 Jan, 2010 1 commit
  4. 06 Jan, 2010 1 commit
  5. 21 Oct, 2009 1 commit
  6. 20 Oct, 2009 1 commit
  7. 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
  8. 05 Oct, 2009 1 commit
  9. 25 Aug, 2009 2 commits
  10. 22 Jun, 2009 2 commits
  11. 20 Jun, 2009 3 commits
  12. 16 Feb, 2009 1 commit
  13. 12 Feb, 2009 1 commit
  14. 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
  15. 04 Sep, 2008 1 commit
  16. 31 Aug, 2008 2 commits
  17. 30 Aug, 2008 2 commits
  18. 28 Aug, 2008 3 commits
  19. 27 Aug, 2008 1 commit
    • Evan Prodromou's avatar
      break up monolithic xmppdaemon into multiple queue handlers · b9f0ea6f
      Evan Prodromou authored
      Eventually, the poor xmppdaemon has become overloaded with extra
      tasks. So, I've broken it up. Now, we have 5 background scripts, and
      more coming:
      
      * xmppdaemon.php - handles incoming XMPP messages only.
      * xmppqueuehandler.php - sends notices from the queue out through XMPP.
      * smsqueuehandler.php - sends notices from the queue out over SMS
      * ombqueuehandler.php - sends notices from the queue out over OMB
      * xmppconfirmhandler.php - sends confirmation requests out over XMPP.
      
      This is in addition to maildaemon.php, which takes incoming messages.
      
      None of these are "true" daemons -- they don't daemonize themselves
      automatically. Use nohup or another tool to background them. monit can
      also be useful to keep them running.
      
      At some point, these might become fork()'ing daemons, able to handle
      more than one notice at a time. For now, I'm just running multiple
      instances, hoping they don't interfere.
      
      darcs-hash:20080827205407-84dde-97884a12f5f4e54c93bc785bd280683d1ee7e749.gz
      b9f0ea6f
  20. 13 Aug, 2008 1 commit
  21. 29 Jul, 2008 1 commit
  22. 09 Jul, 2008 1 commit
  23. 07 Jul, 2008 1 commit
  24. 04 Jul, 2008 1 commit
    • Gina Haeussge's avatar
      Validate action parameter · e3e047b2
      Gina Haeussge authored
      Make sure the action request parameter only consists of a-z, A-Z, 0-9, _ or -
      to discourage tampering with the following require_once.
      
      darcs-hash:20080704194114-2b4f5-2bec30d7d40d7c7bd2c747ef3c805dbf720f6159.gz
      e3e047b2
  25. 22 Jun, 2008 1 commit
    • Evan Prodromou's avatar
      remove check immediate · a69dbe7c
      Evan Prodromou authored
      After getting a lot of problems and bugs with this, I'm removing the
      check_immediate code. Instead, I'm going to add this functionality in
      JavaScript. I think that's a preferred practice, anyways.
      
      darcs-hash:20080622173341-34904-3c406ca9a33dbe3afeacebef1a63d0dd101669c4.gz
      a69dbe7c
  26. 19 Jun, 2008 1 commit