虚拟机 ubuntu 12.04
$ sudo aptitude install stunnel
$ sudo aptitude install squid3
squid3的默认http端口是3128
/etc/stunnel/stunnel.conf中的foreground = yes, 是用来调试用的 如果用superviord来管理stunnel 这个选项也会用得到
/etc/stunnel/stunnel.pem, 这个pair是这样得到的
for (var i = 0; i < 1024 * 1024; i++) { | |
process.nextTick(function () { Math.sqrt(i) } ) | |
} |
var http = require('http'); | |
var server = http.createServer(function(req, res) { | |
// console.log(req); // debug dump the request | |
// If they pass in a basic auth credential it'll be in a header called "Authorization" (note NodeJS lowercases the names of headers in its request object) | |
var auth = req.headers['authorization']; // auth is in base64(username:password) so we need to decode the base64 | |
console.log("Authorization Header is: ", auth); |
# source : http://code.google.com/p/natvpn/source/browse/trunk/stun_server_list | |
# A list of available STUN server. | |
stun.l.google.com:19302 | |
stun1.l.google.com:19302 | |
stun2.l.google.com:19302 | |
stun3.l.google.com:19302 | |
stun4.l.google.com:19302 | |
stun01.sipphone.com | |
stun.ekiga.net |
var WebSocketServer = require('ws').Server; | |
var net = require('net'); | |
var wss = new WebSocketServer({port:9696,host:'0.0.0.0'}); | |
wss.on('connection', function(ws) { | |
console.log('wsconn'); | |
var sock_ready = false; | |
var send_queue = []; | |
var sock = net.createConnection(9695); | |
ws.on('message',function(message){ |
虚拟机 ubuntu 12.04
$ sudo aptitude install stunnel
$ sudo aptitude install squid3
squid3的默认http端口是3128
/etc/stunnel/stunnel.conf中的foreground = yes, 是用来调试用的 如果用superviord来管理stunnel 这个选项也会用得到
/etc/stunnel/stunnel.pem, 这个pair是这样得到的
Clearly ES6 is a huge improvement over ES5, and tools like [6to5][] allow us to use these cool features now. I was reading [Replace CoffeeScript with ES6][replace coffeescript] by [Blake Williams][] and thought it was a great summary of how ES6 solves many of the same problems that CoffeeScript solves; however I'd like to comment on a few of Blake's points and talk about why I'll be sticking with CoffeeScript.
Classes in ES6 (like many of the syntax changes in ES6) are very similar to the CoffeeScript equivalent. To support browsers that are not fully ES5 compliant (e.g. IE8-), however, we still can't really use getters/setters, so ignoring these the comparison is: