Bruno Oliveira da Silva abstractj

This quickstart demonstrates the use of a number of HTML5, CSS3 and JavaScript techniques. The registration form uses client side validation based on the constraints also defined on the model class as well as new input attributes like placeholder and autofocus. The member table is populated using RESTful get calls, client side templating and CSS3 styling.

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

http://amplifyjs.com/

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

http://amplifyjs.com/

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)

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

	Meeting minutes:

	Roadmap review:
	===============

	https://github.com/aerogear/beta.aerogear.org/blob/master/docs/planning/1.0.0/AeroGearAndroid.asciidoc

	M1 progress:
	------------

	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

	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

	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'
	)

	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'
	)