I will give you an example to make the idea a bit clearer:

Imagine you have this request:

GET /profile/picture?profileid=100

In Rails you would define something like this in your routes.rb:

Rails::Routes.define do
  get "/profile/picture" => "profile#get_picture"
end

With ObjectsFramework you only have to define the object called "Profile" and the method "get_picture" (post_picture if it is a POST request, update_picture if it is an UPDATE request, and so on).

So your code would look like this:

class Profile < ObjectsFramework::Object
  def get_picture
    # Your code to get the profile picture
  end
end

ObjectsFramework uses rack under the hood. So I recommend to create a standard "config.ru" (or whatever name you like) and initialize your app there.

How would this work? Let's take a look:

config.ru

# In config.ru
require 'objectsframework'

# Require your other classes (like profile.rb) here too
# For example:
require './profile'

run ObjectsFramework::Server.new

Then you could have an object called "Profile" in a separate file:

profile.rb

class Profile < ObjectsFramework::Object
  def get_picture
    # etc...
  end
end

Now if you would make the following request:

GET /profile/picture

the code in get_picture would be executed. The standard rack, request and response objects are available in a ObjectsFramework::Object, object.

What if I send the request "GET /app/" what instance method would be executed? The method called get_index, instance method of App, would be executed. I'm working on a setting where you can set what happens when a request is sent to "/".

ObjectsFramework is still work in progress, there is a lot that can be made better. I would really like to hear your ideas and opinion.

If you've found some bug, please report via an issue.

Have fun!