hyper-mesh 0.5.3 → 0.5.4

data/lib/synchromesh/synchromesh.rb

@@ -1,159 +0,0 @@
-require 'synchromesh/configuration'
-# Provides the configuration and the two basic routines for the server
-# to indicate that records have changed: after_change and after_destroy
-module HyperMesh
-
-  extend Configuration
-
-  def self.initialize_policies
-    config_reset unless @config_reset_called
-  end
-
-  def self.config_reset
-    @config_reset_called = true
-    Object.send(:remove_const, :Application) if @fake_application_defined
-    policy = begin
-      Object.const_get 'ApplicationPolicy'
-    rescue Exception => e
-      #raise e unless e.is_a?(NameError) && e.message == "uninitialized constant ApplicationPolicy"
-    rescue LoadError
-    end
-    application = begin
-      Object.const_get('Application')
-    rescue LoadError
-    rescue Exception => e
-      #raise e unless e.is_a?(NameError) && e.message == "uninitialized constant Application"
-    end if policy
-    if policy && !application
-      Object.const_set 'Application', Class.new
-      @fake_application_defined = true
-    end
-    @pusher = nil
-    Connection.build_tables
-  end
-
-  define_setting(:transport, :none) do |transport|
-    if transport == :action_cable
-      require 'synchromesh/action_cable'
-      opts[:refresh_channels_every] = :never
-    else
-      require 'pusher' if transport == :pusher
-      opts[:refresh_channels_every] = nil if opts[:refresh_channels_every] == :never
-    end
-  end
-
-  define_setting :opts, {}
-  define_setting :channel_prefix
-  define_setting :client_logging, true
-
-  def self.app_id
-    opts[:app_id] || Pusher.app_id if transport == :pusher
-  end
-
-  def self.key
-    opts[:key] || Pusher.key if transport == :pusher
-  end
-
-  def self.secret
-    opts[:secret] || Pusher.secret if transport == :pusher
-  end
-
-  def self.encrypted
-    opts.key?(:encrypted) ? opts[:encrypted] : true
-  end
-
-  def self.expire_polled_connection_in
-    opts[:expire_polled_connection_in] || (5 * 60)
-  end
-
-  def self.seconds_between_poll
-    opts[:seconds_between_poll] || 0.5
-  end
-
-  def self.expire_new_connection_in
-    opts[:expire_new_connection_in] || 10.seconds
-  end
-
-  def self.refresh_channels_timeout
-    opts[:refresh_channels_timeout] || 5.seconds
-  end
-
-  def self.refresh_channels_every
-    opts[:refresh_channels_every] || 2.minutes
-  end
-
-  def self.refresh_channels
-    new_channels = pusher.channels[:channels].collect do |channel|
-      channel.gsub(/^#{Regexp.quote(HyperMesh.channel)}/,'')
-    end
-  end
-
-  def self.send(channel, data)
-    if !on_server?
-      send_to_server(channel, data)
-    elsif transport == :pusher
-      pusher.trigger("#{HyperMesh.channel}-#{data[1][:channel]}", *data)
-    elsif transport == :action_cable
-      ActionCable.server.broadcast("synchromesh-#{channel}", message: data[0], data: data[1])
-    end
-  end
-
-  def self.on_server?
-    Rails.const_defined? 'Server'
-  end
-
-  def self.send_to_server(channel, data)
-    salt = SecureRandom.hex
-    authorization = HyperMesh.authorization(salt, channel, data[1][:broadcast_id])
-    raise 'no server running' unless Connection.root_path
-    uri = URI("#{Connection.root_path}console_update")
-    http = Net::HTTP.new(uri.host, uri.port)
-    request = Net::HTTP::Post.new(uri.path, 'Content-Type' => 'application/json')
-    if uri.scheme == 'https'
-      http.use_ssl = true
-      http.verify_mode = OpenSSL::SSL::VERIFY_NONE
-    end
-    request.body = {
-      channel: channel, data: data, salt: salt, authorization: authorization
-    }.to_json
-    http.request(request)
-  end
-
-  def self.pusher
-    unless @pusher
-      unless channel_prefix
-        self.transport = nil
-        raise '******** NO CHANNEL PREFIX SET ***************'
-      end
-      @pusher = Pusher::Client.new(
-        opts || { app_id: app_id, key: key, secret: secret }
-      )
-    end
-    @pusher
-  end
-
-  def self.channel
-    "private-#{channel_prefix}"
-  end
-
-  def self.authorization(salt, channel, session_id)
-    secret_key = Rails.application.secrets[:secret_key_base]
-    Digest::SHA1.hexdigest(
-      "salt: #{salt}, channel: #{channel}, session_id: #{session_id}, secret_key: #{secret_key}"
-    )
-  end
-
-  def self.after_commit(operation, model)
-    InternalPolicy.regulate_broadcast(model) do |data|
-      if !HyperMesh.on_server? && Connection.root_path
-        HyperMesh.send_to_server(data[:channel], [operation, data])
-      else
-        Connection.send_to_channel(data[:channel], [operation, data])
-      end
-    end
-  rescue Exception
-    nil  # this is because during db migration we have problems... should investigate more...
-  end
-
-  Connection.transport = self
-end

data/lib/synchromesh/synchromesh_controller.rb

@@ -1,162 +0,0 @@
-module ReactiveRecord
-  ::HyperMesh::Engine.routes.append do
-    HyperMesh.initialize_policies
-
-    module ::WebConsole
-      class Middleware
-      private
-        def acceptable_content_type?(headers)
-          Mime::Type.parse(headers['Content-Type'] || '').first == Mime[:html]
-        end
-      end
-    end if defined? ::WebConsole::Middleware
-
-    module ::Rails
-      module Rack
-        class Logger < ActiveSupport::LogSubscriber
-          unless method_defined? :pre_synchromesh_call
-            alias pre_synchromesh_call call
-            def call(env)
-              if !HyperMesh.opts[:noisy] && env['HTTP_X_SYNCHROMESH_SILENT_REQUEST']
-                Rails.logger.silence do
-                  pre_synchromesh_call(env)
-                end
-              else
-                pre_synchromesh_call(env)
-              end
-            end
-          end
-        end
-      end
-    end if defined?(::Rails::Rack::Logger)
-
-    class HyperMeshController < ::ApplicationController
-
-      protect_from_forgery except: [:console_update]
-
-      def client_id
-        params[:client_id]
-      end
-
-      before_action do
-        session.delete 'synchromesh-dummy-init' unless session.id
-      end
-
-      def channels(user = acting_user, session_id = session.id)
-        HyperMesh::AutoConnect.channels(session_id, user)
-      end
-
-      def can_connect?(channel, user = acting_user)
-        HyperMesh::InternalPolicy.regulate_connection(
-          user,
-          HyperMesh::InternalPolicy.channel_to_string(channel)
-        )
-        true
-      rescue
-        nil
-      end
-
-      def view_permitted?(model, attr, user = acting_user)
-        !!model.check_permission_with_acting_user(user, :view_permitted?, attr)
-      rescue
-        nil
-      end
-
-      def viewable_attributes(model, user = acting_user)
-        model.attributes.select { |attr| view_permitted?(model, attr, user) }
-      end
-
-      [:create, :update, :destroy].each do |op|
-        define_method "#{op}_permitted?" do |model, user = acting_user|
-          begin
-            !!model.check_permission_with_acting_user(user, "#{op}_permitted?".to_sym)
-          rescue
-            nil
-          end
-        end
-      end
-
-      def debug_console
-        if Rails.env.development?
-          render inline: "<style>div#console {height: 100% !important;}</style>\n".html_safe
-          #  "<div>additional helper methods: channels, can_connect? "\
-          #  "viewable_attributes, view_permitted?, create_permitted?, "\
-          #  "update_permitted? and destroy_permitted?</div>\n".html_safe
-          console
-        else
-          head :unauthorized
-        end
-      end
-
-      def subscribe
-        HyperMesh::InternalPolicy.regulate_connection(try(:acting_user), params[:channel])
-        root_path = request.original_url.gsub(/synchromesh-subscribe.*$/, '')
-        HyperMesh::Connection.open(params[:channel], client_id, root_path)
-        head :ok
-      rescue Exception
-        head :unauthorized
-      end
-
-      def read
-        root_path = request.original_url.gsub(/synchromesh-read.*$/, '')
-        data = HyperMesh::Connection.read(client_id, root_path)
-        render json: data
-      end
-
-      def pusher_auth
-        channel = params[:channel_name].gsub(/^#{Regexp.quote(HyperMesh.channel)}\-/,'')
-        HyperMesh::InternalPolicy.regulate_connection(acting_user, channel)
-        response = HyperMesh.pusher.authenticate(params[:channel_name], params[:socket_id])
-        render json: response
-      rescue Exception => e
-        head :unauthorized
-      end
-
-      def action_cable_auth
-        channel = params[:channel_name].gsub(/^#{Regexp.quote(HyperMesh.channel)}\-/,'')
-        HyperMesh::InternalPolicy.regulate_connection(acting_user, channel)
-        salt = SecureRandom.hex
-        authorization = HyperMesh.authorization(salt, channel, client_id)
-        render json: {authorization: authorization, salt: salt}
-      rescue Exception
-        head :unauthorized
-      end
-
-      def connect_to_transport
-        root_path = request.original_url.gsub(/synchromesh-connect-to-transport.*$/, '')
-        render json: HyperMesh::Connection.connect_to_transport(params[:channel], client_id, root_path)
-      end
-
-      def console_update
-        authorization = HyperMesh.authorization(params[:salt], params[:channel], params[:data][1][:broadcast_id]) #params[:data].to_json)
-        return head :unauthorized if authorization != params[:authorization]
-        HyperMesh::Connection.send_to_channel(params[:channel], params[:data])
-        head :no_content
-      rescue
-        head :unauthorized
-      end
-
-      def server_up
-        head :no_content
-      end
-
-    end unless defined? HyperMeshController
-
-    match 'synchromesh-subscribe/:client_id/:channel',
-          to: 'hyper_mesh#subscribe', via: :get
-    match 'synchromesh-read/:client_id',
-          to: 'hyper_mesh#read', via: :get
-    match 'synchromesh-pusher-auth',
-          to: 'hyper_mesh#pusher_auth', via: :post
-    match 'synchromesh-action-cable-auth/:client_id/:channel_name',
-          to: 'hyper_mesh#action_cable_auth', via: :post
-    match 'synchromesh-connect-to-transport/:client_id/:channel',
-          to: 'hyper_mesh#connect_to_transport', via: :get
-    match 'console',
-          to: 'hyper_mesh#debug_console', via: :get
-    match 'console_update',
-          to: 'hyper_mesh#console_update', via: :post
-    match 'server_up',
-          to: 'hyper_mesh#server_up', via: :get
-  end
-end

data/reactive_record_test_app/README.rdoc

@@ -1,261 +0,0 @@
-== 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.