Most of programs will not accept an email using just @localhost as domain.
So, edit /etc/hosts
file to make the domain localhost.com point to your machine, including this content to the file:
127.0.0.1 localhost.com
Most of programs will not accept an email using just @localhost as domain.
So, edit /etc/hosts
file to make the domain localhost.com point to your machine, including this content to the file:
127.0.0.1 localhost.com
var TextOverflow = { | |
crop: function(elm) { | |
var w = elm.width(), | |
t = elm.text(), | |
child; | |
elm.html('<span style="overflow: hidden; white-space: nowrap">'+t+'</span>'); | |
child = elm.children(":first-child"); | |
while (t.length > 0 && child.width() > w) { | |
t = t.substr(0, t.length - 1); |
@Grapes( | |
@Grab(group='com.google.code.gson', module='gson', version='2.1') | |
) | |
import com.google.gson.JsonParser | |
import groovy.json.JsonOutput | |
def feed = 'https://graph.facebook.com/136284706423146/feed?access_token=AAACEdEose0cBAAVRXgYnx5ZA24b9HK9ROQRSJN4EoSZBU8xbI0ZAE9bJmEm6lf2kF9yPcr8t74nuFNKdABNoL88Mc8F9jEpU70Y17O9CpBucO00TbJq' | |
def json = new JsonParser().parse(feed.toURL().text) |
import EXIF from 'exif-js'; | |
const hasBlobConstructor = typeof (Blob) !== 'undefined' && (function checkBlobConstructor() { | |
try { | |
return Boolean(new Blob()); | |
} catch (error) { | |
return false; | |
} | |
}()); |
convert -density 256x256 -background transparent favicon.svg -define icon:auto-resize -colors 256 favicon.ico |
type field = | |
| O | |
| X; | |
type position = (field, field, field, field); | |
type unit = (position, position, position, position); | |
type units = list(unit); |
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on