爱吃猫粮的鱼 tennessine

## gist:3e0e67d5d12ab6638009
Source on GitHub: http://github.com/JoelPM/BidiThrift

A reader posted to the thrift-user mailing list wondering if it was possible for a Thrift RPC server to send messages to the client. The responses indicated that this could be accomplished by polling the server for updates or hosting another Thrift server in the client that could receive RPCs from the server (requires opening another port on the client and handling firewall issues). I responded with a technique I'd used for accomplishing something similar and the responses made me think maybe this would be worth writing up and posting some example code.

Here's my email to the mailing list that describes what I'm doing:

I think I've done something similar to what you're trying to do, and as long as you can commit to using only async messages it's possible to pull it off without having to start a server on the client to accept RPCs from the server.

When your RPC is marked as async the server doesn't send a response and the client doesn't try to read one.

## application.js
var express = require('express');
var redis = require('redis');

const serverType = process.argv[2];
const serverHost = process.argv[3];
const serverPort = parseInt(process.argv[4]);

const redisPort = 6379;
const redisHost = '127.0.0.1';

## application.js
var express = require('express');
var redis = require('redis');

const serverType = process.argv[2];
const serverHost = process.argv[3];
const serverPort = parseInt(process.argv[4]);

const redisPort = 6379;
const redisHost = '127.0.0.1';

## server.js

/**
 * Module dependencies.
 */

var express = require('express')
  , routes = require('./routes')
  , user = require('./routes/user')
  , http = require('http')
  , path = require('path');

## CatFeeder.ino
#include <Servo.h>

Servo myservo;

const int servoPin = 9;
const int buttonPin = 12;
const int ledPin = 13;

void setup() {
  myservo.attach(servoPin);

## haproxy.cfg
global
	#debug
	#daemon
	log 		        127.0.0.1    local0

  defaults
	log  		        global
	option 		        httplog

  frontend unsecured *:80

## highlight_query.sh
#!/bin/sh

curl -XPOST 'http://localhost:9200/example_index/'

curl -XPOST 'http://localhost:9200/example_index/example_type/_mapping?pretty=true' -d \
'{
    "example_type": {
        "Properties": {
            "name": {
                "type": "string",

## on-jsx.markdown

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                tennessine
                / on-jsx.markdown
            
            
              Created
              February 20, 2017 04:41
                — forked from chantastic/on-jsx.markdown
            
              
                JSX, a year in
              
          
    Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I lead the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can'

  
## Readme.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                tennessine
                / Readme.md
            
            
              Created
              March 23, 2017 03:34
                — forked from mxstbr/Readme.md
            
              
                Enable tab completion for JSX with Emmet in Atom
              
          
    Enable tab completion for JSX with Emmet in Atom

This guide assumes you have the emmet and language-babel packages already installed in Atom


Open the keymap.cson file by clicking on Atom -> Keymap… in the menu bar
Add these lines of code to your keymap:

'atom-text-editor[data-grammar~="jsx"]:not([mini])':

  
## gist:03ee7a770d1549e5affc5b1317e512a1
<!DOCTYPE html>
<meta charset="utf-8" />
<title>WebSocket Test</title>
<script language="javascript" type="text/javascript">
var wsUri = "ws://echo.websocket.org/";
var output;

function init() {
  output = document.getElementById("output");
  testWebSocket();
	Source on GitHub: http://github.com/JoelPM/BidiThrift

	A reader posted to the thrift-user mailing list wondering if it was possible for a Thrift RPC server to send messages to the client. The responses indicated that this could be accomplished by polling the server for updates or hosting another Thrift server in the client that could receive RPCs from the server (requires opening another port on the client and handling firewall issues). I responded with a technique I'd used for accomplishing something similar and the responses made me think maybe this would be worth writing up and posting some example code.

	Here's my email to the mailing list that describes what I'm doing:

	I think I've done something similar to what you're trying to do, and as long as you can commit to using only async messages it's possible to pull it off without having to start a server on the client to accept RPCs from the server.

	When your RPC is marked as async the server doesn't send a response and the client doesn't try to read one.
	var express = require('express');
	var redis = require('redis');

	const serverType = process.argv[2];
	const serverHost = process.argv[3];
	const serverPort = parseInt(process.argv[4]);

	const redisPort = 6379;
	const redisHost = '127.0.0.1';

	/**
	* Module dependencies.
	*/

	var express = require('express')
	, routes = require('./routes')
	, user = require('./routes/user')
	, http = require('http')
	, path = require('path');
	#include <Servo.h>

	Servo myservo;

	const int servoPin = 9;
	const int buttonPin = 12;
	const int ledPin = 13;

	void setup() {
	myservo.attach(servoPin);
	global
	#debug
	#daemon
	log 127.0.0.1 local0

	defaults
	log global
	option httplog

	frontend unsecured *:80
	#!/bin/sh

	curl -XPOST 'http://localhost:9200/example_index/'

	curl -XPOST 'http://localhost:9200/example_index/example_type/_mapping?pretty=true' -d \
	'{
	"example_type": {
	"Properties": {
	"name": {
	"type": "string",
	<!DOCTYPE html>
	<meta charset="utf-8" />
	<title>WebSocket Test</title>
	<script language="javascript" type="text/javascript">
	var wsUri = "ws://echo.websocket.org/";
	var output;

	function init() {
	output = document.getElementById("output");
	testWebSocket();