FWIW: I (@Rondy) am not the author of the content presented here, which is an outline from Edmond Lau's book. I've just copy-pasted it from somewhere and saved as a personal gist, before it got popular on newsnews.ycombinator.com. I don't remember where exactly the original source is from and neither could find the author's name, so I cannot give him/her the proper credits.
| #!/bin/bash | |
| # | |
| # Script for updating DNS records on Hurricane Electirc's DNS system (https://dns.he.net). | |
| # | |
| # The record will be updated with the IP address that originates the request. | |
| # | |
| # Usage | |
| # ----- | |
| # | |
| # Create config file `/etc/he-dns-update.conf`: |
| #!/bin/sh | |
| # helper script for making a new CA and signing client (leaf) certs, including making java keystore (JKS) files. useful in creating test fixtures | |
| # | |
| # Example: | |
| # ./mk-test-certs.sh | |
| # ==> Creating new CA: certs/ca.key, certs/ca.crt | |
| # Generating a 2048 bit RSA private key | |
| # ....................................................+++ | |
| # ...............................+++ | |
| # writing new private key to 'certs/ca.key' |
Apesar de Roy Fielding deixar bastante claro que para uma API ser considerada RESTful ela precisa obrigatoriamente seguir todas as constraints definidas em seu trabalho, na prática, muitas vezes precisamos de uma abordagem um pouco mais simples.
Sendo assim, Leonard Richardson propôs um modelo de 4 níveis para que alcancemos uma API REST.
Os níveis 0, 1 e 2 talvez sejam mais familiares, e de fato são mais fáceis de implementar, porém, deve ficar claro que os mesmos não são considerados RESTful.
I hereby claim:
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
