Bruno Oliveira da Silva abstractj

Not exposing implementation details

Looking at this pull request and the related discussion:

the Pipe interface is the only access that endusers should have to a pipe.
the RestAdapter is a HTTP RESTful implementation of the Pipe.
Endusers should not be able do do new RestAdapter(...);

Looking at the discussion of the above PR, it's clear that there exposing internal APIs and/or implementation details has PROs and CONS...

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

CORS Error Response Handling

According to the CORS specification, to indicate an invalid CORS request one simply does not add any CORS specific headers to the response.

There are two situations with regards to CORS Preflight request where this might cause confusion:

The request is using a HTTP Method that is not supported by the server
The request contains headers that are not supported by the server

In both of these cases the response status would be 200, but there will be no CORS-specific response headers. Since there are no CORS-specific headers in the response, the browser assumes the request is invalid, and doesn’t make the actual request. For both of these situations the client would see the same error:

XMLHttpRequest cannot load http://corscontroller-danbev.rhcloud.com/aerogear-controller-demo/delorean. Origin http://corsclient-danbev.rhcloud.com is not allowed by Access-Control-Allow-Origin.

Paging/Querying in AeroGear Controller

This document is intended to discuss a solution for AEROGEAR-645 "Add Query/Paging support on RESTful endpoints".
This dev-aerogear mail list thread was used as a starting point to gather requirements and ideas.

Background

Lets just clarify the two concepts that we are dealing with here, Paging and Query.

Paging

Paging deals with limiting the number of results returned from a single request. One "page" can contain a certain number of items as the result of invoking a request, sometimes referred to the size of a page. Let say you want to limit you the number of result returned to 10 items, this could look something like this:

#AeroGear.AutoConfig

The idea of this utility is to provide a method to automatically configure the client side connections to server resources (Pipeline) via a request for the JSON config to the server from an AeroGear client.

Currently, to set up and use a single connection to the server (pipe) you can use the following:

// Set up a pipeline which contains one pipe using the default REST adapter
var userPipeline = AeroGear.Pipeline( "users" ),
	users = userPipeline.pipes.users;

	#!/bin/sh

	# Usage:
	#
	# * copy this file to the test262 folder
	# * start nailgun server with `ng-server`
	# * run suite with `sh run-test262-nailgun.sh <dynjs-folder>`

	if [ $# = 0 ]
	then

	language: java

	env:
	global:
	- SONATYPE_USERNAME=yourusername
	- secure: "your encrypted SONATYPE_PASSWORD=pass"

	after_success:
	- python addServer.py
	- mvn clean deploy --settings ~/.m2/mySettings.xml

	# Start the old vagrant
	$ vagrant init centos-6.3
	$ vagrant up

	# You should see a message like:
	# [default] The guest additions on this VM do not match the install version of
	# VirtualBox! This may cause things such as forwarded ports, shared
	# folders, and more to not work properly. If any of those things fail on
	# this machine, please update the guest additions and repackage the
	# box.

	<!-- ... -->

	<uses-permission android:name="android.permission.GET_ACCOUNTS" />
	<uses-permission android:name="android.permission.INTERNET" />
	<uses-permission android:name="android.permission.USE_CREDENTIALS" />

	<!-- ... -->