Skip to content

Instantly share code, notes, and snippets.

Avatar

Bruno Oliveira da Silva abstractj

View GitHub Profile
View gist:4540854

Pagination RESTFul API on AeroGear Controller

This document describes pagination in AeroGear. It defines the metadata passed between the client and server.

Parameters

  • offset
    The offset of the first element that should be included in the returned collection. Default value is 0.
  • limit
    The number of elements that should be returned. Default value is 10
  • total
    The total number of elements available.
View gist:4537563

Pagination RESTFul API on AeroGear Controller

This document describes pagination in AeroGear. This includes the client APIs (Android, JavaScript, and iOS) and also the server side (AeroGear Controller)

Parameters

  • offset
    The offset of the first element that should be included in the returned collection. Default value is 0.
  • limit
    The number of elements that should be returned. Default value is 10
  • total
    The total number of elements available.
View token_request_sample.rb
require 'rubygems'
require 'rack/oauth2'
client = Rack::OAuth2::Client.new(
:identifier => YOUR_CLIENT_ID,
:secret => YOUR_CLIENT_SECRET,
:redirect_uri => YOUR_REDIRECT_URI, # only required for grant_type = :code
:host => 'rack-oauth2-sample.heroku.com'
)
View authorization_request_sample.rb
require 'rubygems'
require 'rack/oauth2'
client = Rack::OAuth2::Client.new(
:identifier => YOUR_CLIENT_ID,
:secret => YOUR_CLIENT_SECRET,
:redirect_uri => YOUR_REDIRECT_URI, # only required for grant_type = :code
:host => 'rack-oauth2-sample.heroku.com'
)
View resource_request_sample.rb
require 'rubygems'
require 'rack/oauth2'
def url_for(path)
File.join("https://rack-oauth2-sample-mac.heroku.com", path)
end
resource_of = :user
case resource_of
View resource_request_sample.rb
require 'rubygems'
require 'rack/oauth2'
def url_for(path)
File.join("http://rack-oauth2-sample.heroku.com", path)
end
resource_of = :user
case resource_of
@abstractj
abstractj / gist:4031896
Created Nov 7, 2012 — forked from danbev/gist:4023803
AeroGear Server Side Interfaces
View gist:4031896

AeroGear Server Side Interfaces

This document describes the server side interfaces for AeroGear. Since all interactions use the Http protocol the interfaces in question are resource URLs.

Some of the exposed resource URLs are specific to AeroGear, for example if AeroGear-Security is in use, then there are certain URL that are exposed by default. But for most of the resource URLs the actual composition of the URLs is specific to the server side application. This document's indent is to be a guide for users creating new RESTful server side applications as well as for client developers to know how to interact with RESTful applications (what request/responses will look like).

Transport protocol

The APIs described in this document are based on Hypertext Transfer Protocol, version 1.1 and https is recommended. Please refer to the security section of this document for details why https is important.

Resources

A resource, or an endpoint, is identified by

@abstractj
abstractj / gist:4002565
Created Nov 2, 2012 — forked from danbev/gist:4001775
Handling SecurityProvider Responses in AeroGear-Controller
View gist:4002565

Handling SecurityProvider Responses within AeroGear-Controller

This gist is a follow up a previous gist that investigated using CDI events for handling SecurityProvider responses.

Background

In short, a route can be configured so that only users belonging to certain groups can access the target endpoint. For example:

route()
       .from("/delorean").roles("admin")
       .on(RequestMethod.GET)
@abstractj
abstractj / gist:3912435
Created Oct 18, 2012 — forked from mstruk/gist:3912393
Android Meeting Minutes October 18, 2012
View gist:3912435
Meeting minutes:
Roadmap review:
===============
https://github.com/aerogear/beta.aerogear.org/blob/master/docs/planning/1.0.0/AeroGearAndroid.asciidoc
M1 progress:
------------
@abstractj
abstractj / store-spec.md
Created Jun 27, 2012 — forked from kborchers/store-spec.md
Initial persistence API draft
View store-spec.md

Persistence API - draft 0.1

This is a initial proposal on having a very simple persistence layer

Requirements

  • Persist data on local storage as a type of buffer
  • Enable data to be created/saved/persisted/queryied/removed to/from the server side

References