criskell

Examples of RESTful API calls for E-commerce platforms

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.

Relevant links

JSON-HAL specification: http://stateless.co/hal_specification.html#media_type_identifiers
JSON linking with HAL: http://blog.stateless.co/post/13296666138/json-linking-with-hal

There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules directory) as well as files that are generated (and regenerated) as artifacts of a build process.

All other files should be in your own global gitignore file:

Create a file called .gitignore in your home directory and add any filepath patterns you want to ignore.
Tell git where your global gitignore file is.

Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute .config/git/ignore for .gitignore in your home directory, if you prefer.

Things to remember when compiling/linking C/C++ software

by Angel Leon. March 17, 2015;

Last update on December 14, 2023

Updated on February 27, 2023

Updated August 29, 2019.

Installing ngrok on OSX

For Homebrew v2.6.x and below:

brew cask install ngrok

For Homebrew v2.7.x and above:

GPL3 LICENSE SYNOPSIS

TL;DR* Here's what the license entails:

1. Anyone can copy, modify and distribute this software.
2. You have to include the license and copyright notice with each and every distribution.
3. You can use this software privately.
4. You can use this software for commercial purposes.
5. If you dare build your business solely from this code, you risk open-sourcing the whole code base.

Existential Types in Haskell

I had always been confused by Haskell's implementation of existential types. Until now!

Existential types is the algebraic data type (ADT) equivalent to OOP's data encapsulation. It's a way of hiding a type within a type. Hiding it in such a way that any consumer of the data type won't have any knowledge on the internal property

type StringBool = "true"|"false";


interface AnyNumber { prev?: any, isZero: StringBool };
interface PositiveNumber { prev: any, isZero: "false" };

type IsZero<TNumber extends AnyNumber> = TNumber["isZero"];
type Next<TNumber extends AnyNumber> = { prev: TNumber, isZero: "false" };
type Prev<TNumber extends PositiveNumber> = TNumber["prev"];

	[1 of 1] Compiling IO ( io.hs, io.o )

	8 Lets floated to top level; 0 Lets floated elsewhere; from 11 Lambda groups

	8 Lets floated to top level; 0 Lets floated elsewhere; from 8 Lambda groups

	Total ticks: 507

	107 PreInlineUnconditionally
	2 eta_B1

	{
	"estados": [
	{
	"sigla": "AC",
	"nome": "Acre",
	"cidades": [
	"Acrelândia",
	"Assis Brasil",
	"Brasiléia",
	"Bujari",

	HTTP transfer protocols
	=======================

	Git supports two HTTP based transfer protocols. A "dumb" protocol
	which requires only a standard HTTP server on the server end of the
	connection, and a "smart" protocol which requires a Git aware CGI
	(or server module). This document describes both protocols.

	As a design feature smart clients can automatically upgrade "dumb"
	protocol URLs to smart URLs. This permits all users to have the