rhoconnect 3.4.5 → 4.0.0.beta.10

data/doc/supported-platforms.txt

@@ -2,45 +2,39 @@ Supported Platforms
 ===
 ## Support Matrix
 
+RhoConnect gem is available on the following platforms: 
+
 <table class="device-caps">
   <tr>
     <th>OS</th>
     <th>Distribution</th>
-    <th>Ruby 1.8.7</th>
-    <th>Ruby Enterprise</th>
-    <th>Ruby 1.9.2</th>
     <th>Ruby 1.9.3</th>
+    <th>Ruby 2.0.0</th>
     <th>JRuby</th>
     <th>Environment</th>    
   </tr>
   <tr>
     <td class='cap'>Linux</td>
-    <td> CentOS / RHEL 5 & 6,<br/>Ubuntu 11,<br/>Amazon Linux</td>
-    <td> ruby-1.8.7-p370 </td>
-    <td> ree-1.8.7-2012.02 </td>
-    <td> ruby-1.9.2-p320 </td>
-    <td> ruby-1.9.3-p286 </td>
-    <td> jruby-1.6.7 </td>
+    <td> CentOS / RHEL 5.x & 6.x,<br/>Ubuntu 12.04 </td>
+    <td> ruby-1.9.3-p392 </td>
+    <td class='tbd'> TBD </td>
+    <td class='tbd'> jruby-1.7.3 </td>
     <td>Development &<br/>Production</td>
   </tr>
   <tr>
     <td class='cap'>Mac OS </td>
-    <td> Mac OS X 10.6/10.7 </td>
-    <td> ruby-1.8.7-p370 </td>
-    <td> ree-1.8.7-2012.02 </td>
-    <td> ruby-1.9.2-p320 </td>
-    <td> ruby-1.9.3-p286 </td>
-    <td> jruby-1.6.7 </td>
-    <td>Development &<br/>Production</td>
+    <td> Mac OS X 10.7/10.8 </td>
+    <td> ruby-1.9.3-p392 </td>
+    <td class='tbd'> TBD </td>
+    <td class='tbd'> jruby-1.7.3 </td>
+    <td> Development </td>
   </tr>
   <tr>
     <td class='cap'>Windows</td>
     <td> Windows 7 </td>
-    <td> ruby-1.8.7-p370 </td>
-    <td class='tbd'> TBD </td>
-    <td class='tbd'> TBD </td>
-    <td> ruby-1.9.3-p286 </td>
+    <td> ruby-1.9.3-p392 </td>
     <td class='tbd'> TBD </td>
+    <td class='tbd'> jruby-1.7.3 </td>
     <td>Development</td>
   </tr>
 </table>
@@ -52,22 +46,19 @@ Other Ruby versions and releases might work with RhoConnect gem, but there are n
 RhoConnect for Windows is supported only in development environments. The components you should have for this environment are:
 
 * Ruby 1.9.3
-* Redis 2.4.x
+* Redis 2.6.x
 * Latest RhoConnect and Rhodes gems
 * Eclipse 3.6 with latest RhoStudio plugin, or RhoStudio for Windows 32-bit
-* Make 3.18
+* Make 3.81
 * DevKit for Windows (or other Windows development environment)
 
-RhoConnect for Linux and Mac OS X is supported for both development and production environments. The components you should have for this environment are:
+RhoConnect for Linux is supported for both development and production environments. 
+On Linux servers RhoConnect is available in the format of [Debian (deb) and Red Hat (rpm) packages](http://edgedocs.rhomobile.com/rhoconnect/deploying) for Ubuntu and CentOS respectively.
+RhoConnect Mac OS X is supported in development environment. 
+The components you should have for this environment are:
 
 * Ruby 1.9.3
 * Nginx HTTP server (1.3.x)
-* Redis data store (2.4.x)
+* Redis data store (2.6.x)
 * Thin application server
 * RhoConnect gem with all required dependencies
-
-
-## Known Issues
-
-* If you deploy your RhoConnect application deploy on <b>Heroku</b>, then use new [Cedar](http://devcenter.heroku.com/articles/cedar) stack. The Bamboo stack is older than the widespread adoption of bundler, 
-so on Bamboo your application is not invoked in the context of your bundle and might not works properly.

data/doc/testing.txt

@@ -4,7 +4,7 @@ RhoConnect provides a [spec](http://rspec.info/) framework for [behavior driven
 
 ## Example Spec
 
-Here is a simple example spec for the [rhostore product adapter](http://github.com/rhomobile/store-server/blob/master/sources/product.rb):
+Here is a simple example model spec for the [rhostore product adapter](http://github.com/rhomobile/store-server/blob/master/sources/product.rb):
 
 	:::ruby
 	it "should process Product query" do
@@ -12,7 +12,7 @@ Here is a simple example spec for the [rhostore product adapter](http://github.c
 	  query_errors.should == {}
 	end
 
-This simple spec runs the query method of our product adapter and verifies the result is greater than one object and has no errors.
+This simple spec runs the query method of our product adapter model and verifies the result is greater than one object and has no errors.
 
 The full code listing for this product_spec is available [on github](http://github.com/rhomobile/store-server/blob/master/spec/sources/product_spec.rb).
 
@@ -21,7 +21,7 @@ From your application's root folder:
 	
 	:::term
   	$ rhoconnect spec
-	[05:51:48 PM 2012-04-19] Rhoconnect Server v3.2.0 started...
+	[05:51:48 PM 2012-04-19] Rhoconnect Server v4.0.1 started...
 	Product
 	  it should behave like SpecHelper
 	    should process Product query (PENDING: No reason given)
@@ -41,17 +41,32 @@ From your application's root folder:
 This will also automatically generate an rcov report under 'coverage' if you have rcov installed (currently only Mac/Linux support rcov).
 
 ## Test API
-For the most up-to-date Test API, please see the [rdocs](http://rdoc.info/projects/rhomobile/rhoconnect).
 
-### `setup_test_for(adapter,user_id)`
-Initializes the source adapter under test for a given user, typically in a before(:each) block
+The [RhoConnect Source Adapter Model Test API](/rhoconnectapi/test-api) provides the following methods to perform spec tests.
+
+ * [setup_test_for](/rhoconnectapi/test-api-ruby#setuptestfor) - Executes the adapter's query method and returns the master document.
+ * [test_query](/rhoconnectapi/test-api-ruby#testquery) - Executes the adapter's query method and returns the master document.
+ * [query_errors](/rhoconnectapi/test-api-ruby#queryerrors) - Returns any errors stored in redis for the previous source adapter query.
+ * [test_create](/rhoconnectapi/test-api-ruby#testcreate) - Executes the adapter's create method with a provided record and returns the object string from the create method.
+ * [create_errors](/rhoconnectapi/test-api-ruby#createerrors) - Returns the result of the adapter's create method..
+ * [test_update](/rhoconnectapi/test-api-ruby#testupdate) - Execute the source adapter's update method.
+ * [update_errors](/rhoconnectapi/test-api-ruby#updateerrors) - Returns any errors stored in redis from the previous source adapter update.
+ * [test_delete](/rhoconnectapi/test-api-ruby#testdelete) - Execute the source adapter's delete method.
+ * [delete_errors](/rhoconnectapi/test-api-ruby#deleteerrors) - Returns any errors stored in redis from the previous source adapter delete.
+ * [md](/rhoconnectapi/test-api-ruby#md) - Returns the master document (:md) for the source adapter stored in redis.
+ * [cd](/rhoconnectapi/test-api-ruby#cd) - Returns the client document (:cd) for the source adapter + client under test.
+
+## Example of setup_test_for
+
+This example initializes a source adapter model named Product under test for a user named testuser.
 	
 	:::ruby
 	# 'testuser' will be used by rest of the specs
 	setup_test_for(Product,'testuser') 
 
-### `test_query`
-Executes the adapter's query method and returns the master document (:md) stored in redis.
+## Example of test_query
+
+The `test_query` method executes the model's query method and returns the master document (:md) stored in redis.
 
 For example, if your source adapter query method was:
 	
@@ -82,8 +97,9 @@ For example, if your source adapter query method was:
 	  }
 	}
 
-### `query_errors`
-Returns any errors stored in redis for the previous source adapter query.
+## Example of query_errors
+
+Returns any errors stored in redis for the previous model's query.
 
 For example:  
 
@@ -93,10 +109,10 @@ For example:
 		  "message" => "error connecting to web service!"
 	  }
 	}
-	
 
-### `test_create(record)`
-Execute's the adapter's create method with a provided record and returns the object string from the create method.  If the create method returns a string, then a link will be saved for the device next time it synchronizes.  This link can be tested here.
+## Example of test_create
+
+The `test_create` method executes the model's create method with a provided record and returns the object string from the create method. If the create method returns a string, then a link will be saved for the device next time it synchronizes.
 
 For example, in your spec:
 	:::ruby
@@ -125,23 +141,17 @@ For example, in your spec:
 	@s.pass_through = 'true'
 	new_product = test_create(@product)
 	new_product.should == {'processed' => ["temp-id"]}.to_json
-	
-### `create_errors`
-This will return the result of the adapter's create method.  The master document (:md) should also contain the new record.
-Returns any errors stored in redis from the previous source adapter create (same structure as query errors).
 
-### `test_update(record)`
-Execute the source adapter's update method.  Takes a record as hash of hashes (object_id => object)
+## Example of test_update
 
-For example:
+This example executes the model's update method, calling the adapter's update method for object_id '4'.
 	
 	:::ruby
 	test_update({'4' => {'price' => '$199.99'}})
 	update_errors.should == {}
 	test_query
 	md[product_id]['price'].should == '$199.99'
- 
-This will call the adapter's update method for object_id '4'.
+
 
 **NOTE: To test the master document, you will need to run `test_query` as shown above.**
 
@@ -152,14 +162,10 @@ For example, in your spec:
 	record = {'4'=> { 'price' => '199.99' }}
 	@s.pass_through = 'true'
 	test_update(record).should == {'processed' => ["4"]}.to_json
-	
-### `update_errors`
-Returns any errors stored in redis from the previous source adapter update (same structure as query errors).
 
-### `test_delete(record)`
-Execute the source adapter's delete method.  Takes a record as hash of hashes (object_id => object).
+## Example of test_delete
 
-For example:
+This example executes the source model's delete method, calling the adapter's delete method for product '4'.
 	
 	:::ruby
 	@product = {
@@ -173,13 +179,10 @@ For example:
 	delete_errors.should == {}
 	md.should == {}
  
-This will call the adapter's delete method for product '4'.
-
 **NOTE: The master document (:md) will be updated and can be verified as shown above.**
 
-If you have set [pass through](http://docs.rhomobile.com/rhoconnect/source-adapters#pass-through) to true, the delete method will return a json hash of the object id deleted.
+If you have set [pass through](http://docs.rhomobile.com/rhoconnect/source-adapters#pass-through) to true, the delete method will return a json hash of the object id deleted. You could have the following code in your spec.
 
-For example, in your spec:
 	:::ruby
 	@product = {
 	  'name' => 'iPhone',
@@ -192,13 +195,9 @@ For example, in your spec:
 	@s.pass_through = 'true'
 	test_update(record).should == {'processed' => ["4"]}.to_json
 
-### `delete_errors`
-Returns any errors stored in redis from the previous source adapter delete (same structure as query errors).
-
-### `md`
-Returns the master document (:md) for the source adapter stored in redis.  This is equivalent to the @result hash of hashes structure.
+## Example of md
 
-For example:
+The md method returns the master document (:md) for the source adapter model stored in redis. This is equivalent to the @result hash of hashes structure.
 	
 	:::ruby
 	md.should == { 
@@ -212,11 +211,10 @@ For example:
 	  }
 	}
 
-### `cd`
-Returns the client document (:cd) for the source adapter + client under test.  The master document (:md) and client document (:cd) should be equal after the query is executed.
+## Example of cd
+
+This example shows that the master document (:md) and client document (:cd) should be equal after the query is executed.
 
-For example:
-	
 	:::ruby
 	test_query.size.should > 0
 	md.should == cd

data/doc/tutorial.txt

@@ -52,11 +52,14 @@ Now you can run redis and your RhoConnect app:
 
 If everything went well you should see:
 
-	[01:48:15 PM 2012-08-04] Rhoconnect Server v3.3.4 started...
+	[01:48:15 PM 2012-08-04] Rhoconnect Server v4.0.1 started...
 
 ## Defining RhoConnect Source Adapters
 
-Once RhoConnect is installed we're ready to build a RhoConnect source to integrate with our backend application. To define a RhoConnect source you just need to identify a handful of operations to interact with your backend data source: login, query, sync, create, update, delete and logoff. For more information please see the [RhoConnect source adapter](/rhoconnect/source-adapters) documentation.
+Once RhoConnect is installed we're ready to build a RhoConnect source adapter to integrate with our backend application. Each Source Adapter consists of two pieces - Controller and Model.
+Source Adapter Controller is a designated Sinatra application which is responsible for adding and routing the incoming requests to your Source Adapter. Controller instantiates the model and calls its methods when necessary. 
+Source Adapter Model is a placeholder for your Source Adapter business logic. This is where you implement the interaction with your backend service.
+To define a RhoConnect model you just need to identify a handful of operations to interact with your backend data source: login, query, sync, create, update, delete and logoff. For more information please see the [RhoConnect source adapter model](/rhoconnect/source-adapters) documentation.
 
 ### Generating the Source Adapter from RhoStudio
 
@@ -76,8 +79,11 @@ After pressing the Finish button, you'll see the RhoConnect source adapter gener
 
 You should now have files for the source adapter in your storeserver application. The files are organized as follows:
 
-* product.rb -> This is the source adapter file which contains the login, query, create, update, delete and logoff methods to call a backend service. You will add code to implement these methods.
-* product_spec.rb -> This file contains the spec with tests which relate to our source adapter.
+* `product.rb` - This is the source adapter's model file which contains the login, query, create, update, delete and logoff methods to call a backend service. You will add code to implement these methods.
+* `product_controller.rb` - This is the source adapter's controller file which defines the RhoConnect application web end point and adds SYNC routes into your Source Adapter. You may add your custom routes here.
+* `product_spec.rb` - This file contains the spec with tests which relate to our source adapter's model.
+* `product_controller_spec.rb` - This file contains the spec with tests which relate to our source adapter's controller.
+
 
 You can open these files for editing by clicking on them in the Project Explorer.
 
@@ -90,20 +96,38 @@ Then run the command to generate a source adapter for the product model. The pro
 	:::term
 	$ rhoconnect source product
 
-which generates two files, the product adapter and the product spec:
+which generates product controller, product model and the corresponding spec files:
 
 	Generating with source generator:
-     	[ADDED]  sources/product.rb
-     	[ADDED]  spec/sources/product_spec.rb
+     	[ADDED]  models/ruby/product.rb
+     	[ADDED]  controllers/ruby/product_controller.rb
+     	[ADDED]  spec/models/ruby/product_spec.rb
+     	[ADDED]  spec/controllers/ruby/product_controller_spec.rb
 
-You can use the command line to navigate to the sources/product.rb file in your RhoConnect application folder.
+You can use the command line to navigate to files in your RhoConnect application folder.
 
-### Understanding the Source Adapter File
+### Understanding the Controller File
 
-The generated source adapter file (in this case, product.rb) is similar to the code listing below. It has code to raise an exception for any required method. Note that you don't need to use the source generator; you can create a Ruby file and place it into your lib directory. The class name (in this case, product) of the RhoConnect source adapter must match that of the Rhodes client model.
+The generated source adapter's controller file (in this case, product_controller.rb) is similar to the code listing below. 
+Its purpose is to define the RhoConnect application web end point and to register the corresponding routes. 
+Under the hood - it's an isolated Sinatra application designated to handle all incoming Product requests.
 
 	:::ruby
-	class Product < SourceAdapter
+	class ProductController < Rhoconnect::Controller::Base
+	  register Rhoconnect::EndPoint
+
+	  # add all SYNC routes
+	  register Rhoconnect::Handler::Sync
+
+	  # add your custom Product routes here
+	end
+
+### Understanding the Model File
+
+The generated source adapter's model file (in this case, product.rb) is similar to the code listing below. It has code to raise an exception for any required method.
+
+	:::ruby
+	class Product < Rhoconnect::Model::Base
 	  def initialize(source)
 	    super(source)
 	  end
@@ -119,7 +143,7 @@ The generated source adapter file (in this case, product.rb) is similar to the c
 	    #   "1"=>{"name"=>"Acme", "industry"=>"Electronics"},
 	    #   "2"=>{"name"=>"Best", "industry"=>"Software"}
 	    # }
-	    raise SourceAdapterException.new("Please provide some code to read records from the backend data source")
+	    raise Rhoconnect::Model::Base::Exception.new("Please provide some code to read records from the backend data source")
 	  end
 
 	  def sync
@@ -165,9 +189,9 @@ The next step is for you to fill in the login, query, create, update, delete and
 
 ## A RhoConnect Query
 
-If you're doing a readonly non-authenticated source adapter, you can just write one method, query, to retrieve records as we describe here. The following is a sample query method to interact with a simple product catalog (available at http://rhostore.herokuapp.com) that exposes a REST interface.  Note that RhoConnect can work with any protocol. This example shows JSON over HTTP with a REST interface, since that is common. The RhoConnect source adapter is Ruby code and there are ruby libraries (aka gems) that will make it easy to connect to and parse whatever you need -- the query code would just be slightly different.
+If you're doing a readonly non-authenticated source adapter, you can just write one model method, query, to retrieve records as we describe here. The following is a sample query method to interact with a simple product catalog (available at <http://rhostore.herokuapp.com>) that exposes a REST interface.  Note that RhoConnect can work with any protocol. This example shows JSON over HTTP with a REST interface, since that is common. The RhoConnect source adapter model is Ruby code and there are ruby libraries (aka gems) that will make it easy to connect to and parse whatever you need -- the query code would just be slightly different.
 
-For a more complete example of rewriting the source adapter methods (such as create, update, and delete), refer to the [source adapter example](/rhoconnect/source-adapters#sample-adapter) in the RhoConnect Developer Reference.
+For a more complete example of rewriting the source adapter model methods (such as create, update, and delete), refer to the [source adapter model example](/rhoconnect/source-adapters#sample-model) in the RhoConnect Developer Reference.
 
 Our sample web service for returning all products in the catalog (http://rhostore.herokuapp.com/products.json) returns data like this:
 
@@ -199,17 +223,17 @@ Our sample web service for returning all products in the catalog (http://rhostor
 	  }
 	]
 
-The Ruby code for parsing that data, sources.product.rb, is listed below. It uses the standard Ruby JSON library and the RestClient library for easy access to the REST web service. This example uses the id of the product record as the hash key. Note that the key for this hash must be a string and the value can be any set of name-value pairs which are represented as a Ruby hash. The instance variable @result must be set by the query method to this "hash of hashes", indexed by a unique identifier, so that the base SourceAdapter class sync method can populate Redis data store.
+The Ruby code for parsing that data, `models/ruby/product.rb`, is listed below. It uses the standard Ruby JSON library and the RestClient library for easy access to the REST web service. This example uses the id of the product record as the hash key. Note that the key for this hash must be a string and the value can be any set of name-value pairs which are represented as a Ruby hash. The instance variable @result must be set by the query method to this "hash of hashes", indexed by a unique identifier, so that the base model class `sync` method can populate the Redis data store.
 
-You can edit sources/product.rb within RhoStudio, or you can navigate to it within your RhoConnect application folder and edit it with a text editor.
+You can edit models/ruby/product.rb within RhoStudio, or you can navigate to it within your RhoConnect application folder and edit it with a text editor.
 
-We need to declare the standard libraries that we are using at the top of the sources/product.rb file:
+We need to declare the standard libraries that we are using at the top of the `models/ruby/product.rb` file:
 
 	:::ruby
 	require 'json'
 	require 'rest_client'
 
-For convenience, we'll add an instance variable @base which contains the base URL of the web service and sets the value in the constructor:
+For convenience, we'll add an instance variable `@base` which contains the base URL of the web service and sets the value in the constructor:
 
 	:::ruby
   	def initialize(source)
@@ -227,7 +251,7 @@ Then fill in the query method:
       if parsed
         parsed.each do |item|
           key = item["product"]["id"].to_s
-          @result[key]=item["product"]
+          @result[key] = item["product"]
         end
       end
     end
@@ -251,7 +275,15 @@ For example:
 
 ## Testing Sync from the Client
 
-Make sure you are running redis. From the folder in which you app is located, run this command.
+From RhoStudio, select your RhoConnect project in the Project Explorer, and select Run->Run Configurations… from the menu. The Run Configurations window appears.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-tutorial/run-configurations-rc.png"/>
+
+To create a new build configuration for your application, select RhoConnect Application. Then either right-click on RhoConnect Application or click the New button. A new configuration appears under RhoConnect Application. Click the Run button to run it.
+
+<img src="http://rhodocs.s3.amazonaws.com/rhoconnect-tutorial/run-config-rhoconnect-new-rc.png"/>
+
+If you are working from the command line, first make sure you are running redis. From the folder in which your app is located, run this command.
 
 	:::term
 	$ rhoconnect redis-start
@@ -261,9 +293,7 @@ Then start (or restart) your server:
 	:::term
    	$ rhoconnect start
 
-**Note: The RhoConnect application must be run from the command line. It does not run from RhoStudio.**
-
-The code for the source adapter loads when the server starts. If you have a syntax error in your Ruby code, it will be reported and the server will not start; however, if you have a runtime error, that will not be reported until the source adapter is called.
+The code for the source adapter model loads when the server starts. If you have a syntax error in your Ruby code, it will be reported and the server will not start; however, if you have a runtime error, that will not be reported until the model's method is called.
 
 Make sure your server URL is configured in the Rhodes app. If your server is running on YourIPAddress with the port 9292, the following line should be at the bottom of your corresponding Rhodes app, storemanager/rhoconfig.txt:
 
@@ -290,10 +320,10 @@ To sync with the RhoConnect server, the Rhodes client must log in. The Rhodes ge
 1. From the home page in the Rhodes app, click on the login button in the upper right corner. Alternatively, you can click on the tool icon at the bottom of the screen to go to the Settings screen, and click the login button from there.
 <img src="http://rhodocs.s3.amazonaws.com/rhoconnect-tutorial/storemanager-rhosimulator-home-arrows.png"/>
 
-2. Login using any name & password. The generated code allows any login, but you can modify that in application.rb.
+2. Login using any username & password. The generated code allows any username, but you can modify that in `application_controller.rb`.
 <img src="http://rhodocs.s3.amazonaws.com/rhoconnect-tutorial/rhosimulator-login.png"/>
 
-3. If login is successful, you will see a Client ID in the settings screen. The ClientID is generated the first time you log in and is stored in the client database.  It serves as a unique identifier which is required for rhoconnect. (Note: this value will persist across logins, but if you reset the client database or the user re-installs the app, a new ClientID will be generated.)
+3. If login is successful, you will see a Client ID in the settings screen. The ClientID is generated the first time you log in and is stored in the client database.  It serves as a unique identifier which is required for RhoConnect. (Note: this value will persist across logins, but if you reset the client database or the user re-installs the app, a new Client ID will be generated.)
 4. Sync is triggered automatically. Click on the home icon and then select "Products" and you should see the list of product records from the server.
 
 This example shows a couple of iPhone products.
@@ -310,7 +340,7 @@ For your create method, the RhoConnect server will pass you a hash containing th
 	  "brand" => "Acme"
 	}
 
-The RhoConnect sources/product.rb create method will be called once for every object that has been created on the client since the last sync.  Your code for create (or edit or delete) needs to use this populated array to do its work.  Below is an example of a create method against the [rhostore](http://rhostore.herokuapp.com), which accepts an HTTP POST to perform a create action. The create method should return a unique id string for the object for it to be later modifiable by the client. If no id is returned, then you should treat the client object as read only, because it will not be able to be synchronized.
+The RhoConnect `models/ruby/product.rb` create method will be called once for every object that has been created on the client since the last sync.  Your code for create (or edit or delete) needs to use this populated array to do its work.  Below is an example of a create method against the [rhostore](http://rhostore.herokuapp.com), which accepts an HTTP POST to perform a create action. The create method should return a unique id string for the object for it to be later modifiable by the client. If no id is returned, then you should treat the client object as read only, because it will not be able to be synchronized.
 
 	:::ruby
 	def create(create_hash)
@@ -328,48 +358,33 @@ The RhoConnect sources/product.rb create method will be called once for every ob
       JSON.parse(new_record)["product"]["id"].to_s
     end
 
-You will need to restart RhoConnect to reload the source adapter after modifying code. Note that the object will be created on the client right away, but it will be sent to the server on the next sync.
+You will need to restart RhoConnect to reload the model after modifying code. Note that the object will be created on the client right away, but it will be sent to the server on the next sync.
 
 ## Authentication
 
-The generated RhoConnect application code includes a file at the root of the directory called "application.rb" which contains a hook for authentication. The complete file looks like this:
+The generated RhoConnect application code includes an ApplicationController class which resides in the `controllers/ruby/application_controller.rb` which contains a route for authentication. The complete file looks like this:
 
 	:::ruby
-	class Application < Rhoconnect::Base
-  	  class << self
-        def authenticate(username,password,session)
-      	  true # do some interesting authentication here...
-        end
-
-        # Add hooks for application startup here
-        # Don't forget to call super at the end!
-        def initializer(path)
-          super
-        end
-
-        # Calling super here returns rack tempfile path:
-        # i.e. /var/folders/J4/J4wGJ-r6H7S313GEZ-Xx5E+++TI
-        # Note: This tempfile is removed when server stops or crashes...
-        # See http://rack.rubyforge.org/doc/Multipart.html for more info
-        #
-        # Override this by creating a copy of the file somewhere
-        # and returning the path to that file (then don't call super!):
-        # i.e. /mnt/myimages/soccer.png
-        def store_blob(blob)
-          super #=> returns blob[:tempfile]
-        end
-      end
-    end
+	class ApplicationController < Rhoconnect::Controller::AppBase
+  	  register Rhoconnect::EndPoint
+
+  	  post "/login", :rc_handler => :authenticate do
+    		login = params[:login]
+    		password = params[:password]
+    		true # do some interesting authentication here...
+  	  end
+	end
 
-    Application.initializer(ROOT_PATH)
 
-If your back end web service requires authentication, add code to the authenticate method and return true if authentication was successful or false to deny access to the application from this client. For example:
+If your back end web service requires authentication, add code to the `/login` route and return true if authentication was successful or false to deny access to the application from this client. For example:
 
 	:::ruby
-	def authenticate(username, password, session)
+	post '/login', :rc_handler => :authenticate do
+	  login = params[:login]
+      password = params[:password]
   	  # ... connect to backend using API and authenticate ...
   	  if success
-        # save the data for later use in the source adapter
+        # save the data for later use
         Store.put_value("username:#{username}:token",username)
       end
       return success

data/examples/simple/Gemfile

@@ -3,7 +3,7 @@ source 'http://rubygems.org'
 # load rhoconnect from relative path
 gem 'rhoconnect', :path => '../../'
 
-gemfile_path = File.join(File.dirname(__FILE__), '..', '..', 'generators','templates', 'application', ".rcgemfile")
+gemfile_path = File.join(File.dirname(__FILE__), '..', '..', 'generators','templates', 'application', "rcgemfile")
 begin 
   eval(IO.read(gemfile_path)) 
 rescue Exception => e

data/examples/simple/application.rb

@@ -3,18 +3,18 @@ class Application < Rhoconnect::Base
     def authenticate(username,password,session)
       true # do some interesting authentication here...
     end
-    
+
     # Add hooks for application startup here
     # Don't forget to call super at the end!
     def initializer(path)
       super
     end
-    
+
     # Calling super here returns rack tempfile path:
     # i.e. /var/folders/J4/J4wGJ-r6H7S313GEZ-Xx5E+++TI
     # Note: This tempfile is removed when server stops or crashes...
     # See http://rack.rubyforge.org/doc/Multipart.html for more info
-    # 
+    #
     # Override this by creating a copy of the file somewhere
     # and returning the path to that file (then don't call super!):
     # i.e. /mnt/myimages/soccer.png
@@ -22,8 +22,7 @@ class Application < Rhoconnect::Base
       super #=> returns blob[:tempfile]
     end
 
-    def ans_authenticate(username,password)
-      puts "ans_authenticate - user: #{username} password: #{password}"
+    def rps_authenticate(username,password)
       true
     end
   end

data/examples/simple/my_server.rb

@@ -1,6 +1,6 @@
-# FIXME: This is a temporary server to handle ans token registration
+# FIXME: This is a temporary server to handle rps token registration
 class MyServer < Rhoconnect::Server
-  post '/ans/token' do
+  post '/rps/token' do
   	user = "tuser"
   	User.create(:login => user)
   	current_app.users << user

data/examples/simple/settings/settings.yml

@@ -5,7 +5,7 @@
     :partition_type: app    
     :poll_interval: 500
   Product:
-   :partition_type: user    
+   :partition_type: user
    :poll_interval: 500
 
 :development: