These utilities are grouped into related files, for simpler copy & paste to your scripts.
A couple of helper functions to convert to & from A1 notation.
It's more than you probably think
A user types the URL http://www.example.com into a browser.
The browser sends a request for the IP address of www.example.com to its local resolver (stub-resolver).
The stub-resolver queries the locally configured DNS Resolver for the IP address of www.example.com.
$.recordCount.value = 99 |
#!/bin/bash | |
outfile=${*: -1:1} | |
remove=1 | |
echo "$@" > $outfile; "${@:1:$(($#-remove))}" >> $outfile |
var gulp = require('gulp'), | |
gutil = require('gulp-util'), | |
sass = require('gulp-sass'), | |
rubysass = require('gulp-ruby-sass'), | |
fileinclude = require('gulp-file-include'), | |
rename = require('gulp-rename'), | |
notify = require('gulp-notify'), | |
livereload = require('gulp-livereload'), | |
lr = require('tiny-lr'), | |
connect = require('gulp-connect'), |
<?php | |
ini_set('display_errors', 1); | |
/** | |
* This script check how PHP makes HTTPS (SSL/TLS) requests using PHP Streams | |
* or cURL. Configuration options are passed as GET parameters, for example: | |
* http://localhost/checksslcontext.php?reconfigure=1 | |
* | |
* Configuration: | |
* http://localhost/checksslcontext.php | |
* Basic PHP Streams using file_get_contents(). Default settings. |
http://amundsen.com/media-types/collection/examples/
This format takes into consideration collections (much like Siren). It also takes into consideration versioning. However, I'm not certain version matters in the data set if it pertains to an API version. That is best left being in the API URL. It could pertain to collection version, but I'm not sure the point. Documentation says each collection should have a version - but says nothing more about meaning or why.
Items are clearly distinct in this format and are organizationally positioned separate from links.
This is by far the most collision free structure.
However, the data format itself is a bit strange...Every field being an array. Data is always an array of objects. I understand the flexibility this presents and am not 100% against it. I just believe it's perhaps not needed as things could change based on the client application.