These are chat archives for gregaubs/API-people

9th
Mar 2015
gregaubs
@gregaubs
Mar 09 2015 11:44
pdf page 34 is where it gets to routing specifically
Amil Vasishtha
@amilvasishtha
Mar 09 2015 12:16
var myHonda = {color: "red", wheels: 4, engine: {cylinders: 4, size: 2.2}};
myCar["make"] = "Ford";
myCar["model"] = "Mustang";
myCar["year"] = 1969;
Anita
@Neats29
Mar 09 2015 15:43

Here’s how to update your fork directly from GitHub (as shown in the video above):

Open your fork on GitHub.
Click on Pull Requests.
Click on New Pull Request. By default, GitHub will compare the original with your fork, and there shouldn’t be anything to compare if you didn’t make any changes.
Click on switching the base (if no changes were made in the fork) or click Edit and switch the base manually. Now GitHub will compare your fork with the original, and you should see all the latest changes.
Click on Create to create a pull request for this comparison and assign a predictable name to your pull request (e.g., Update from original).
Click on Send pull request.
Scroll down and click Merge pull request and finally Confirm merge. If your fork didn’t have any changes, you will be able to merge it automatically.

gregaubs
@gregaubs
Mar 09 2015 16:15
  • REST are a series of constraints:
    Uniform Interface
    The uniform interface constraint defines the interface between clients and servers. It simplifies and decouples the architecture, which enables each part to evolve independently
    Stateless
    the necessary state to handle the request is contained within the request itself, whether as part of the URI, query-string parameters, body, or headers.
    Cacheable
    As on the World Wide Web, clients can cache responses. Responses must therefore, implicitly or explicitly, define themselves as cacheable, or not, to prevent clients reusing stale or inappropriate data in response to further requests.
    Client-Server
    The uniform interface separates clients from servers. Clients are not concerned with data storage, which remains internal to each server, so that the portability of client code is improved. Servers are not concerned with the user interface or user state, so that servers can be simpler and more scalable.
    Layered System
    A client cannot ordinarily tell whether it is connected directly to the end server, or to an intermediary along the way.
    Code on Demand (optional)
    Servers are able to temporarily extend or customize the functionality of a client by transferring logic to it that it can execute. Examples of this may include compiled components such as Java applets and client-side scripts such as JavaScript.
Amil Vasishtha
@amilvasishtha
Mar 09 2015 16:16