README.v0.0.1.md

oversip-mod-mysql

IMPORTANT

This is the documentation for oversip-mod-mysql version 0.0.1, just compatible with OverSIP version >= 1.2.0 and < 1.3.0. For new versions of OverSIP check the documentation of the current version.

Overview

oversip-mod-mysql provides an easy to use MySQL connector for OverSIP proxy based on mysql2 driver. The library allows both pure async style (via callbacks) or serial style (by using em-synchrony Gem).

Check the mysql2 documentation for the exact syntax and usage of the MySQL queries.

API

Method OverSIP:M:Mysql.add_pool(options, db_data)

Creates a MySQL connection pool. Parameters:

• options: A mandatory Hash with the following fields:

  • :name: Mandatory field. Must be a Symbol with the name for this pool.
  • :pool_size: The number of parallel MySQL connections to perform. By default 10.
  • :synchrony: Whether to use em-synchrony or not. By default false.

• db_data: A mandatory Hash that will be passed to Mysql2::EM::Client.new.

NOTE: There is no need to pass the option :async => true in db_data. That is automatically done by the library.

Method OverSIP:M:Mysql.pool(name)

Retrieves a previously created pool with the given name. Raises an ArgumentError if the given name does not exist in the list of created pools.

Pure async style usage

When creating a pool with options[:synchrony] => false (default behaviour) the obtained pool is a EventMachine::Pool instance and thus, it requires the following usage:

Example

On top of /etc/oversip/server.rb:

require "oversip-mod-mysql"

def (OverSIP::SystemEvents).on_initialize
  OverSIP::M::Mysql.add_pool(
    {
      :name => :my_async_db,
      :pool_size => 5,
      :synchrony => false
    },
    {
      :host => "localhost",
      :username => "oversip",
      :password => "xxxxxx",
      :database => "oversip",
      :cast_booleans => true,
      :symbolize_keys => true
    }
  )
end

Somewhere within the OverSIP::SipEvents.on_request() method in /etc/oversip/server.rb:

pool = OverSIP::M::Mysql.pool(:my_async_db)

begin
  pool.perform do |db_conn|
    query = db_conn.aquery "SELECT * FROM users WHERE user = \'#{request.from.user}\'"

    query.callback do |result|
      log_info "DB async query result: #{result.to_a.inspect}"
      if result.any?
        # Add a X-Header with value the 'custom_header' field of the table row:
        request.set_header "X-Header", result.first["custom_header"]
        proxy = ::OverSIP::SIP::Proxy.new
        proxy.route request
      else
        request.reply 404, "User not found in DB"
      end
    end

    query.errback do |error|
      log_error "DB async query error: #{error.inspect}"
      request.reply 500, "DB async query error"
    end
  end

rescue ::Mysql2::Error => e
  log_error "DB async query error:"
  log_error e
  request.reply 500, "DB async query error"
end

Sync style usage with em-synchrony

When creating a pool with options[:synchrony] => true the obtained pool is a EventMachine::Synchrony::ConnectionPool instance.

Please ensure you properly understand how em-synchrony works. Specially take into account that just the code within the EM.synchrony do [...] end block is executed serially. Code placed after that block is executed immediately, this is, before the serial code is executed. So if you want to use serial style coding write all your logic code within a EM.synchrony do [...] end block.

• For more information about em-synchrony usage check Untangling Evented Code with Ruby Fibers.

Example

On top of /etc/oversip/server.rb:

require "oversip-mod-mysql"

def (OverSIP::SystemEvents).on_initialize
  OverSIP::M::Mysql.add_pool(
    {
      :name => :my_sync_db,
      :pool_size => 5,
      :synchrony => true
    },
    {
      :host => "localhost",
      :username => "oversip",
      :password => "xxxxxx",
      :database => "oversip",
      :cast_booleans => true,
      :symbolize_keys => true
    }
  )
end

Somewhere within the OverSIP::SipEvents.on_request() method in /etc/oversip/server.rb:

EM.synchrony do
  pool = OverSIP::M::Mysql.pool(:my_sync_db)

  begin
    result = pool.query "SELECT * FROM users WHERE user = \'#{request.from.user}\'"
    log_info "DB sync query result: #{result.to_a.inspect}"
    if result.any?
      # Add a X-Header with value the 'custom_header' field of the table row:
      request.set_header "X-Header", result.first["custom_header"]
      proxy = ::OverSIP::SIP::Proxy.new :proxy_out
      proxy.route request
    else
      request.reply 404, "User not found in DB"
    end

  rescue ::Mysql2::Error => e
    log_error "DB sync query error:"
    log_error e
    request.reply 500, "DB sync query error"
  end
end

Using async and sync styles together

A pool created with OverSIP:M:Mysql.add_pool() method must be sync or async. However the user can set two pools, the first one async and the second one sync.

When a sync pool is created, the library loads em-synchrony/mysql2 which overrides the Mysql2::EM::Client#query() method. So if at least one of your pools uses sync style then you must use the Mysql2::EM::Client#aquery() method for the async pool (which is an alias of the original query() method).

Dependencies

• Ruby > 1.9.2.
• oversip Gem >= 1.2.0.
• MySQL development library (the package libmysqlclient-dev in Debian/Ubuntu).

Installation

~$ gem install oversip-mod-mysql

Author

Iñaki Baz Castillo [email protected] (Github @ibc).