| <?php | |
| /** | |
| * SplClassLoader implementation that implements the technical interoperability | |
| * standards for PHP 5.3 namespaces and class names. | |
| * | |
| * http://groups.google.com/group/php-standards/web/final-proposal | |
| * | |
| * // Example which loads classes for the Doctrine Common package in the | |
| * // Doctrine\Common namespace. |
These examples are type 3 RESTful API requests and responses. The JSON-HAL specification is used to implement HATEOAS.
Some of the examples are based on my work as architect of the RESTful API at http://www.hautelook.com. All proprietary information has been removed.
| <!doctype html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>App Redirection</title> | |
| </head> | |
| <body> | |
| <!-- | |
| NOTE: This was a great hack in days gone by, but now both Apple and Google have improved their support for custom | |
| protocol handlers. |
| <?php | |
| use Respect\Http\Hypermedia as hy; | |
| //All synopses from movies featuring Will Smith as an actor. | |
| hy::with("netflix", "http://api.netflix.com/") | |
| ->with("schema", "http://schemas.netflix.com/") | |
| ->get("netflix/catalog/people", array('term' => 'Will Smith')) | |
| ->rel("schema/catalog/person/filmography") | |
| ->rel("schema/catalog/titles/synopsis")->send(); |
| { | |
| "_links": { | |
| "self": { "href": "/orders" }, | |
| "next": { "href": "/orders?page=2" }, | |
| "find": { "href": "/orders{?id}", "templated": true } | |
| }, | |
| "_embedded": { | |
| "orders": [{ | |
| "_links": { | |
| "self": { "href": "/orders/123" }, |
| package com.example.helloworld.resources; | |
| import javax.jws.WebMethod; | |
| @javax.jws.WebService( | |
| name = "AddNumbersPortType", | |
| serviceName = "AddNumbersService", | |
| targetNamespace = "http://duke.example.org") | |
| @javax.jws.soap.SOAPBinding( | |
| style = javax.jws.soap.SOAPBinding.Style.DOCUMENT, |
| package com.mao.jaxb.util; | |
| import java.io.IOException; | |
| import java.io.InputStream; | |
| import java.io.OutputStream; | |
| import java.lang.annotation.Annotation; | |
| import java.lang.reflect.Type; | |
| import javax.ws.rs.WebApplicationException; | |
| import javax.ws.rs.core.MediaType; | |
| import javax.ws.rs.core.MultivaluedMap; |
| <?php | |
| /* | |
| * Copyright 2008 Google Inc. | |
| * | |
| * Licensed under the Apache License, Version 2.0 (the "License"); | |
| * you may not use this file except in compliance with the License. | |
| * You may obtain a copy of the License at | |
| * | |
| * http://www.apache.org/licenses/LICENSE-2.0 | |
| * |
| import java.util.ArrayList; | |
| import java.util.Iterator; | |
| import java.util.Locale; | |
| import android.content.Context; | |
| import android.content.Intent; | |
| import android.database.AbstractCursor; | |
| import android.database.Cursor; | |
| import android.support.v4.app.FragmentActivity; | |
| import android.text.TextUtils; |
| Secure sessions are easy, but not very well documented. | |
| Here's a recipe for secure sessions in Node.js when NginX is used as an SSL proxy: | |
| The desired configuration for using NginX as an SSL proxy is to offload SSL processing | |
| and to put a hardened web server in front of your Node.js application, like: | |
| [NODE.JS APP] <- HTTP -> [NginX] <- HTTPS -> [PUBLIC INTERNET] <-> [CLIENT] | |
| Edit for express 4.X and >: Express no longer uses Connect as its middleware framework, it implements its own now. |
