| Installing CYGWIN with SSH | |
| 1) Download cygwin setup.exe from http://www.cygwin.com | |
| - Execute setup.exe | |
| - Install from internet | |
| - Root directory: `c:\cygwin` + all users | |
| - Local package directory: use default value | |
| - Select a mirror to download files from | |
| - Select these packages: | |
| - editors > xemacs 21.4.22-1 | |
| - net > openssh 6.1-p |
mkdir -p /usr/local/etc/nginx/sites-{enabled,available}
cd /usr/local/etc/nginx/sites-enabled
ln -s ../sites-available/default.conf
ln -s ../sites-available/default-ssl.conf
File locations:
nginx.conf to /usr/local/etc/nginx/default.conf and default-ssl.conf to /usr/local/etc/nginx/sites-availablehomebrew.mxcl.nginx.plist to /Library/LaunchDaemons/
| type T struct { | |
| A int | |
| B string | |
| } | |
| t := T{23, "skidoo"} | |
| s := reflect.ValueOf(&t).Elem() | |
| typeOfT := s.Type() | |
| for i := 0; i < s.NumField(); i++ { |
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.
| /* | |
| * Getting timelines by Twitter Streaming API | |
| */ | |
| #include <iostream> | |
| #include <stdio.h> | |
| #include <stdlib.h> | |
| #include <string.h> | |
| #include <unistd.h> | |
| #include <oauth.h> | |
| #include <curl/curl.h> |
On VMWare fusion, running an Ubuntu Xenial VM, which has a copy of your OS X public SSH key -- the script to build the image will add it to the generated image -- grab the script at https://github.com/zyga/devtools/blob/master/ubuntu-image to create a new image:
./ubuntu-image.sh --developer-mode pc
qemu-img convert pc-devel.img -O vmdk snappy.vmdk
| // An intersting pattern for testing, but you can use the check anywhere | |
| import "testing" | |
| func TestCheckingChannel(t *testing.T) { | |
| stop := make(chan bool) | |
| // Testing some fucntion that SHOULD close the channel | |
| func (stop chan bool) { | |
| close(chan) | |
| }(stop) |
# Key considerations for algorithm "RSA" ≥ 2048-bit
openssl genrsa -out server.key 2048
# Key considerations for algorithm "ECDSA" ≥ secp384r1
# List ECDSA the supported curves (openssl ecparam -list_curves)
States. The final frontier. These are the voyages of an enterprising developer. Her eternal mission: to explore strange new techniques, to seek out better ways to engineer for mental models and new design patterns. To boldly go where a few awesome devs have gone before.
So you’ve found our poignant guide to SCXML and surely you’re wondering “Why should I want to go out of my way to use formal state machines?” or something like that. Hopefully this introduction addresses that kind of question.