Watch a table for changes and push a notification with a payload describing the change.
In the Postgres shell:
-- Create the functions
Watch a table for changes and push a notification with a payload describing the change.
In the Postgres shell:
-- Create the functions
This is roughly the same test run in both casper and nightwatch.
I've been looking for the best Linux backup system, and also reading lots of HN comments.
Instead of putting pros and cons of every backup system I'll just list some deal-breakers which would disqualify them.
Also I would like that you, the HN community, would add more deal breakers for these or other backup systems if you know some more and at the same time, if you have data to disprove some of the deal-breakers listed here (benchmarks, info about something being true for older releases but is fixed on newer releases), please share it so that I can edit this list accordingly.
#!/usr/bin/env python | |
import numpy | |
from numpy.distutils.system_info import get_info | |
import sys | |
import timeit | |
print("version: %s" % numpy.__version__) | |
print("maxint: %i\n" % sys.maxsize) | |
info = get_info('blas_opt') |
2015-01-29 Unofficial Relay FAQ
Compilation of questions and answers about Relay from React.js Conf.
Disclaimer: I work on Relay at Facebook. Relay is a complex system on which we're iterating aggressively. I'll do my best here to provide accurate, useful answers, but the details are subject to change. I may also be wrong. Feedback and additional questions are welcome.
Relay is a new framework from Facebook that provides data-fetching functionality for React applications. It was announced at React.js Conf (January 2015).
"""Demo of streaming requests with Tornado. | |
This script features a client using AsyncHTTPClient's body_producer | |
feature to slowly produce a large request body, and two server | |
handlers to receive this body (one is a proxy that forwards to the | |
other, also using body_producer). | |
It also demonstrates flow control: if --client_delay is smaller than | |
--server_delay, the client will eventually be suspended to allow the | |
server to catch up. You can see this in the logs, as the "client |
(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.
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS
REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
# -*- coding: utf-8 | |
from time import sleep, time | |
from tornado.httpserver import HTTPServer | |
from tornado.ioloop import IOLoop | |
from tornado.web import Application, asynchronous, RequestHandler | |
from multiprocessing.pool import ThreadPool | |
from tornado import gen | |
pool = ThreadPool(10) |
import os | |
import json | |
import httplib | |
import time | |
VERSION = "0.1.0" | |
class ClientSession: | |
def __init__(self, server, user, source=None, catalog=None, schema=None, debug=False): | |
self.server = server |