kennethkalmer

DaemonKit::AMQP.run do
  # Inside this block we're running inside the reactor setup by the
  # amqp gem. Any code in the examples (from the gem) would work just
  # fine here.

  MQ.prefetch(10)

  # Uncomment this for connection keep-alive
  AMQP.conn.connection_status do |status|
    DaemonKit.logger.debug("AMQP connection status changed: #{status}")

kennethkalmer

require 'rubygems'
require 'mq'

Signal.trap('INT') { AMQP.stop { EM.stop } }
Signal.trap('TERM') { AMQP.stop { EM.stop } }

AMQP.start do

  amq = MQ.new
  c1 = 0

kennethkalmer

function(doc) {
  if(doc.type && doc.type == 'Email' && doc.unread == '1') {
    emit( doc.recipient, 1 )
  }
}

kennethkalmer

# multithreaded daemon example
#
#
#   daemon_kit foo
#

# Two classes that do the work, they live in lib/

# lib/foo.rb
class Foo

kennethkalmer

class CrazyIdea < OpenWFE::ProcessDefinition
  sequence do
    _loop :break_if => "${f:completed}" do
      # This is the queue, getting popped by a REST call. The person who did the pop
      # will have the workitem field 'winner_of_the_lock' set to their details, so the
      # next participant is dynamic based on that field value.
      queue_participant

      #
      participant "${f:winner_of_the_lock}", :timeout => '1d'

kennethkalmer

#
# daemon-kit stack configuration
#
# severe pseudo-code example
#

#
# config/environment.rb (shared stack)
#
DaemonKit::Initializer.run do |config|

kennethkalmer

#
# Somewhere in a daemon where activerecord is being used
#

class MyARDaemon

  include DaemonKit::ActiveRecord

  def something_ar
    MyModel.find(:all)

kennethkalmer

#
# Requirements:
# * ruote-2.1.10 or later
# * ruote-amqp-2.1.10 or later
# * daemon-kit-0.1.8rc3 or later
#

require 'rubygems'

require 'ruote'

kennethkalmer

#
# AMQP generated daemon (this would be the file in libexec/)
#
# NOTE 1: This config would be adapted to be more ruote-friendly
# 
# NOTE 2: This would be the names of queues used in the process definition, or JID's to use
#
# NOTE 3: This would be responsible for handling the processesing
#

kennethkalmer

#
# The code below is lifted from a daemon generated with daemon-kit.
# 
# It is responsible for executing various commands on Linux servers to provision
# and manage hosting services for several hundred clients on each server. Messages
# are delivered to 'identity'-based queues, where each agent can tune into more than
# one queue depending on that services they offer.
#
# The original messages are JSON objects, representing workitems for the
# ruote workflow engine. There is some intermediary code that slices up the workitems