sync_client 0.0.14

data/lib/sync_client/poller.rb

@@ -0,0 +1,12 @@
+module SyncClient
+  class Poller
+
+    def self.run
+      new.run
+    end
+
+    def run
+      SyncClient::Worker.new.work
+    end
+  end
+end

data/lib/sync_client/publisher.rb

@@ -0,0 +1,52 @@
+module SyncClient
+  module Publisher
+    extend ActiveSupport::Concern
+
+    included do
+      before_update :publish_update
+      after_destroy :publish_destroy
+      after_create :publish_create
+    end
+
+    module ClassMethods
+      def publish_changes_of(*attributes, options)
+        @queue_publisher = SyncClient::QueuePublisher.new unless @queue_publisher
+        @queue_publisher.add_publisher(attributes, options)
+      end
+
+      attr_reader :queue_publisher
+    end
+
+    def queue_publisher
+      self.class.queue_publisher
+    end
+
+    def publish_update
+      queue_publisher.publish(:update, self)
+    end
+
+    def publish_destroy
+      queue_publisher.publish(:destroy, self)
+    end
+
+    def publish_create
+      queue_publisher.publish(:create, self)
+    end
+
+    def publisher_attributes
+      if self.respond_to?(:aliased_fields)
+        self.attributes.inject({}) { |attrs, (raw_key, raw_value)|
+          if raw_key =='_id'
+            attrs['id'] = raw_value
+          else
+            attrs[self.aliased_fields.invert.fetch(raw_key) { raw_key }] = raw_value
+          end
+          attrs
+        }
+      else
+        self.attributes
+      end
+    end
+  end
+end
+

data/lib/sync_client/queue_publisher.rb

@@ -0,0 +1,28 @@
+module SyncClient
+  class QueuePublisher
+    attr_accessor :sync_queues
+
+    def initialize
+      self.sync_queues = []
+    end
+
+    def add_publisher(attributes, options)
+      self.sync_queues << SyncClient::SyncQueue.new(attributes, options)
+    end
+
+    def publish(action, object)
+      sync_queues.each do |sync_queue|
+        SyncClient.logger.info("#{sync_queue.inspect}")
+        queue_message(action, object, sync_queue.queue).publish if sync_queue.publishable?(action, object)
+      end
+    end
+
+    def queue_message(action, object, queue)
+      SyncClient::PubMessage.new(
+        :queue => queue,
+        :action => action,
+        :object_type => object.class.to_s,
+        :object_attributes => object.publisher_attributes)
+    end
+  end
+end

data/lib/sync_client/sync_queue.rb

@@ -0,0 +1,32 @@
+module SyncClient
+  class SyncQueue
+    attr_accessor :attributes
+    attr_accessor :queue
+    attr_accessor :callbacks
+    attr_accessor :options
+
+    CALLBACK_DEFAULTS = [:update, :create, :destroy]
+
+    def initialize(attributes, options)
+      @attributes = attributes
+      @queue = options[:to]
+      @callbacks = options[:for] || CALLBACK_DEFAULTS
+      @options = options
+    end
+
+    def publishable?(action, object)
+      callbacks.include?(action) and update?(action, object) and resolve_condition(object)
+    end
+
+    def update?(action, object)
+      action.to_s != 'update' || attributes.any?{|attr| object.send("#{attr}_changed?")}
+    end
+
+    def resolve_condition(object)
+      return true if options[:if].nil? && options[:unless].nil?
+      result = options[:if] == true || (options[:if].respond_to?(:call) && options[:if].call(object)) if options.has_key?(:if)
+      result = options[:unless] == false || (options[:unless].respond_to?(:call) && !options[:unless].call(object)) if options.has_key?(:unless)
+      result
+    end
+  end
+end

data/lib/sync_client/task_queue/delayed_job.rb

@@ -0,0 +1,7 @@
+module SyncClient
+  class DelayedJob
+    def self.enqueue(job, message)
+      job.delay.perform(message.instance_values)
+    end
+  end
+end

data/lib/sync_client/task_queue/inline_task_queue.rb

@@ -0,0 +1,7 @@
+module SyncClient
+  class InlineTaskQueue
+    def self.enqueue(job, message)
+      job.perform(message.instance_values)
+    end
+  end
+end

data/lib/sync_client/task_queue/resque.rb

@@ -0,0 +1,7 @@
+module SyncClient
+  class Resque
+    def self.enqueue(job, message)
+      ::Resque.enqueue(job, message)
+    end
+  end
+end

data/lib/sync_client/tasks.rb

@@ -0,0 +1,9 @@
+require 'queuel'
+namespace :sync_client do
+  task :setup
+
+  desc "Start a queue poller"
+  task :poll => :setup do
+    SyncClient::Worker.new.work
+  end
+end

data/lib/sync_client/version.rb

@@ -0,0 +1,3 @@
+module SyncClient
+  VERSION = "0.0.14"
+end

data/lib/sync_client/worker.rb

@@ -0,0 +1,15 @@
+module SyncClient
+  class Worker
+    def work
+      puts "starting queuel worker"
+      ::Queuel.receive do |message|
+        begin
+          SyncClient::SubMessage.new(message.body).process if message and message.body
+        rescue Exception => e
+          SyncClient.logger.error("Exception Occurred:\n\t#{e.message}\n\t#{e.backtrace}")
+          false
+        end
+      end
+    end
+  end
+end

data/test/app/pub_message_test.rb

@@ -0,0 +1,33 @@
+require 'test_helper'
+
+class PubMessageTest < ActiveSupport::TestCase
+  context "PubMessage" do
+    context "ClassMethods" do
+      setup do
+        @player = Player.create(:name => 'joe')
+        queue_publisher = SyncClient::QueuePublisher.new
+        @message = queue_publisher.queue_message(:action, @player, 'dummy')
+      end
+
+      should "queue publish" do
+        SyncClient.background_task_queue.expects(:enqueue).with(Jobs::SyncClientJobs::Publish, @message).returns(true)
+        @message.publish
+      end
+
+      should "copy object queues" do
+        assert_not_nil @message.queue
+      end
+
+      should "wrap object type with service" do
+        assert_equal "Dummy::Player", @message.object_type_with_service
+      end
+
+      should "push message to queues" do
+        queuel = Queuel.with(@message.queue)
+        Queuel.expects(:with).with(@message.queue).once.returns(queuel)
+        @message.synchronous_publish
+      end
+
+    end
+  end
+end

data/test/app/service_resource/base_test.rb

@@ -0,0 +1,18 @@
+require 'test_helper'
+
+class BaseTest < ActiveSupport::TestCase
+  context "Base" do
+    context "ClassMethods" do
+      setup do
+        @game = Game.new(:name => 'game', :id => 1, :invalid => 'sdfas')
+      end
+
+      should "respond to meta_resource_name with defined resource" do
+        assert_equal 'game', @game.name
+        assert_equal 1, @game.id
+        assert_equal false, @game.respond_to?(:invalid)
+      end
+
+    end
+  end
+end

data/test/app/sub_message_test.rb

@@ -0,0 +1,42 @@
+require 'test_helper'
+
+class SubMessageTest < ActiveSupport::TestCase
+  context "SubMessage" do
+    context "ClassMethods" do
+      setup do
+        @message = ::SyncClient::SubMessage.new(
+          :object_type => 'Dummy::Game',
+          :object_attributes => {:id => 1, :name => 'game', :invalid => 'invalid'},
+          :action => :update)
+
+        @message.stubs(:handler).with
+      end
+
+      should "send action to valid message" do
+        assert_equal true, @message.process
+      end
+
+      should "skip message object " do
+        @message.object_type = 'invalid'
+        assert_equal true, @message.process
+      end
+
+      should "skip message action" do
+        @message.action = 'invalid'
+        assert_equal true, @message.process
+      end
+
+      should "create message_handler with attributes" do
+        assert_equal Game, @message.handler_class.handler
+        assert_equal [:update, :create, :destroy], @message.handler_class.actions
+      end
+
+      should "access errors if set" do
+        @message.action = 'destroy'
+        assert_equal true, @message.process
+        assert_not_nil @message.error
+      end
+
+    end
+  end
+end

data/test/dummy/README.rdoc

@@ -0,0 +1,261 @@
+== Welcome to Rails
+
+Rails is a web-application framework that includes everything needed to create
+database-backed web applications according to the Model-View-Control pattern.
+
+This pattern splits the view (also called the presentation) into "dumb"
+templates that are primarily responsible for inserting pre-built data in between
+HTML tags. The model contains the "smart" domain objects (such as Account,
+Product, Person, Post) that holds all the business logic and knows how to
+persist themselves to a database. The controller handles the incoming requests
+(such as Save New Account, Update Product, Show Post) by manipulating the model
+and directing data to the view.
+
+In Rails, the model is handled by what's called an object-relational mapping
+layer entitled Active Record. This layer allows you to present the data from
+database rows as objects and embellish these data objects with business logic
+methods. You can read more about Active Record in
+link:files/vendor/rails/activerecord/README.html.
+
+The controller and view are handled by the Action Pack, which handles both
+layers by its two parts: Action View and Action Controller. These two layers
+are bundled in a single package due to their heavy interdependence. This is
+unlike the relationship between the Active Record and Action Pack that is much
+more separate. Each of these packages can be used independently outside of
+Rails. You can read more about Action Pack in
+link:files/vendor/rails/actionpack/README.html.
+
+
+== Getting Started
+
+1. At the command prompt, create a new Rails application:
+       <tt>rails new myapp</tt> (where <tt>myapp</tt> is the application name)
+
+2. Change directory to <tt>myapp</tt> and start the web server:
+       <tt>cd myapp; rails server</tt> (run with --help for options)
+
+3. Go to http://localhost:3000/ and you'll see:
+       "Welcome aboard: You're riding Ruby on Rails!"
+
+4. Follow the guidelines to start developing your application. You can find
+the following resources handy:
+
+* The Getting Started Guide: http://guides.rubyonrails.org/getting_started.html
+* Ruby on Rails Tutorial Book: http://www.railstutorial.org/
+
+
+== Debugging Rails
+
+Sometimes your application goes wrong. Fortunately there are a lot of tools that
+will help you debug it and get it back on the rails.
+
+First area to check is the application log files. Have "tail -f" commands
+running on the server.log and development.log. Rails will automatically display
+debugging and runtime information to these files. Debugging info will also be
+shown in the browser on requests from 127.0.0.1.
+
+You can also log your own messages directly into the log file from your code
+using the Ruby logger class from inside your controllers. Example:
+
+  class WeblogController < ActionController::Base
+    def destroy
+      @weblog = Weblog.find(params[:id])
+      @weblog.destroy
+      logger.info("#{Time.now} Destroyed Weblog ID ##{@weblog.id}!")
+    end
+  end
+
+The result will be a message in your log file along the lines of:
+
+  Mon Oct 08 14:22:29 +1000 2007 Destroyed Weblog ID #1!
+
+More information on how to use the logger is at http://www.ruby-doc.org/core/
+
+Also, Ruby documentation can be found at http://www.ruby-lang.org/. There are
+several books available online as well:
+
+* Programming Ruby: http://www.ruby-doc.org/docs/ProgrammingRuby/ (Pickaxe)
+* Learn to Program: http://pine.fm/LearnToProgram/ (a beginners guide)
+
+These two books will bring you up to speed on the Ruby language and also on
+programming in general.
+
+
+== Debugger
+
+Debugger support is available through the debugger command when you start your
+Mongrel or WEBrick server with --debugger. This means that you can break out of
+execution at any point in the code, investigate and change the model, and then,
+resume execution! You need to install ruby-debug to run the server in debugging
+mode. With gems, use <tt>sudo gem install ruby-debug</tt>. Example:
+
+  class WeblogController < ActionController::Base
+    def index
+      @posts = Post.all
+      debugger
+    end
+  end
+
+So the controller will accept the action, run the first line, then present you
+with a IRB prompt in the server window. Here you can do things like:
+
+  >> @posts.inspect
+  => "[#<Post:0x14a6be8
+          @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>,
+       #<Post:0x14a6620
+          @attributes={"title"=>"Rails", "body"=>"Only ten..", "id"=>"2"}>]"
+  >> @posts.first.title = "hello from a debugger"
+  => "hello from a debugger"
+
+...and even better, you can examine how your runtime objects actually work:
+
+  >> f = @posts.first
+  => #<Post:0x13630c4 @attributes={"title"=>nil, "body"=>nil, "id"=>"1"}>
+  >> f.
+  Display all 152 possibilities? (y or n)
+
+Finally, when you're ready to resume execution, you can enter "cont".
+
+
+== Console
+
+The console is a Ruby shell, which allows you to interact with your
+application's domain model. Here you'll have all parts of the application
+configured, just like it is when the application is running. You can inspect
+domain models, change values, and save to the database. Starting the script
+without arguments will launch it in the development environment.
+
+To start the console, run <tt>rails console</tt> from the application
+directory.
+
+Options:
+
+* Passing the <tt>-s, --sandbox</tt> argument will rollback any modifications
+  made to the database.
+* Passing an environment name as an argument will load the corresponding
+  environment. Example: <tt>rails console production</tt>.
+
+To reload your controllers and models after launching the console run
+<tt>reload!</tt>
+
+More information about irb can be found at:
+link:http://www.rubycentral.org/pickaxe/irb.html
+
+
+== dbconsole
+
+You can go to the command line of your database directly through <tt>rails
+dbconsole</tt>. You would be connected to the database with the credentials
+defined in database.yml. Starting the script without arguments will connect you
+to the development database. Passing an argument will connect you to a different
+database, like <tt>rails dbconsole production</tt>. Currently works for MySQL,
+PostgreSQL and SQLite 3.
+
+== Description of Contents
+
+The default directory structure of a generated Ruby on Rails application:
+
+  |-- app
+  |   |-- assets
+  |   |   |-- images
+  |   |   |-- javascripts
+  |   |   `-- stylesheets
+  |   |-- controllers
+  |   |-- helpers
+  |   |-- mailers
+  |   |-- models
+  |   `-- views
+  |       `-- layouts
+  |-- config
+  |   |-- environments
+  |   |-- initializers
+  |   `-- locales
+  |-- db
+  |-- doc
+  |-- lib
+  |   |-- assets
+  |   `-- tasks
+  |-- log
+  |-- public
+  |-- script
+  |-- test
+  |   |-- fixtures
+  |   |-- functional
+  |   |-- integration
+  |   |-- performance
+  |   `-- unit
+  |-- tmp
+  |   `-- cache
+  |       `-- assets
+  `-- vendor
+      |-- assets
+      |   |-- javascripts
+      |   `-- stylesheets
+      `-- plugins
+
+app
+  Holds all the code that's specific to this particular application.
+
+app/assets
+  Contains subdirectories for images, stylesheets, and JavaScript files.
+
+app/controllers
+  Holds controllers that should be named like weblogs_controller.rb for
+  automated URL mapping. All controllers should descend from
+  ApplicationController which itself descends from ActionController::Base.
+
+app/models
+  Holds models that should be named like post.rb. Models descend from
+  ActiveRecord::Base by default.
+
+app/views
+  Holds the template files for the view that should be named like
+  weblogs/index.html.erb for the WeblogsController#index action. All views use
+  eRuby syntax by default.
+
+app/views/layouts
+  Holds the template files for layouts to be used with views. This models the
+  common header/footer method of wrapping views. In your views, define a layout
+  using the <tt>layout :default</tt> and create a file named default.html.erb.
+  Inside default.html.erb, call <% yield %> to render the view using this
+  layout.
+
+app/helpers
+  Holds view helpers that should be named like weblogs_helper.rb. These are
+  generated for you automatically when using generators for controllers.
+  Helpers can be used to wrap functionality for your views into methods.
+
+config
+  Configuration files for the Rails environment, the routing map, the database,
+  and other dependencies.
+
+db
+  Contains the database schema in schema.rb. db/migrate contains all the
+  sequence of Migrations for your schema.
+
+doc
+  This directory is where your application documentation will be stored when
+  generated using <tt>rake doc:app</tt>
+
+lib
+  Application specific libraries. Basically, any kind of custom code that
+  doesn't belong under controllers, models, or helpers. This directory is in
+  the load path.
+
+public
+  The directory available for the web server. Also contains the dispatchers and the
+  default HTML files. This should be set as the DOCUMENT_ROOT of your web
+  server.
+
+script
+  Helper scripts for automation and generation.
+
+test
+  Unit and functional tests along with fixtures. When using the rails generate
+  command, template test files will be generated for you and placed in this
+  directory.
+
+vendor
+  External libraries that the application depends on. Also includes the plugins
+  subdirectory. If the app has frozen rails, those gems also go here, under
+  vendor/rails/. This directory is in the load path.