Sergey Prokhorov seriyps

Moved to own repo:

https://github.com/mkorthof/ipset-country

I'm looking to collect information on why certain functionality found in Erlang/OTP is usually handled instead by a third party library in people's projects.

This could be bugs, missing functionality, poor interface, performance, etc.

Examples off the top of my head that need expanding on are:

httpc
httpd
http_uri

Connecting to serial port (com port) over network

(Serial port or com port? - Serial ports are often refered as COM ports. It is the same to be short. You can read abut it in the Wiki article )

The problem
The solution in theory
WINDOWS
- Server
- Client

Driver Signature

HTTP and related specifications

This gist is deprecated in favor of https://github.com/ninenines/cowboy/blob/master/doc/src/guide/specs.asciidoc which has a formatted version at https://ninenines.eu/docs/en/cowboy/2.0/guide/specs/

HTTP

IANA Registries

#HERO4 Black Wifi hacking, ep 1

URL for streaming: http://10.5.5.9/gp/gpExec?p1=gpTsFeeder&a1=%22%22&c1=restart&p2=gpStream&a2=%22%22&c2=restart

###Android decopilation APK

AUDIO_INPUT_MODE: http://10.5.5.9/camera/AI
AUTO_POWER_OFF: http://10.5.5.9/camera/AO
BACPAC_BATTERY_LEVEL: http://10.5.5.9/bacpac/blx
BACPAC_CV: http://10.5.5.9/bacpac/cv

Erlang Tracing: more than you wanted to know

Rough Outline

What can be traced?
How can trace events be specified?
"match specifications": twisty passages, all alike
WTF, can I just use DTrace and drink my coffee/beer/whisky in peace?
Trace delivery mechanisms: pick one of two

	-module(gen_tcp2).

	-export([listen/2, accept/1, accept/2,
	connect/3, connect/4,
	send/2, recv/1, recv/2, recv/3,
	close/1]).

	-export([run/0, run/2]).

	%% Naive gen_tcp shim over the socket API

	-module(string_eqc).
	-compile([export_all,nowarn_export_all]).
	-include_lib("eqc/include/eqc.hrl").

	%%%
	%%% Test most new functions in the new string module (PR #1330).
	%%%


	flat_chardata() ->

	/* automatically generated by rust-bindgen */

	pub type ErlNifUInt64 = ::libc::c_ulong;
	pub type ErlNifSInt64 = ::libc::c_long;
	pub type ERL_NIF_TERM = ::libc::c_ulong;
	pub type ERL_NIF_UINT = ERL_NIF_TERM;
	pub enum Struct_enif_environment_t { }
	pub type ErlNifEnv = Struct_enif_environment_t;
	#[repr(C)]
	pub struct ErlNifFunc {

	-module(niftest).
	-export([add/2]).
	-on_load(init/0).

	init() ->
	ok = erlang:load_nif("./nif", 0).

	add(_, _) ->
	exit(nif_library_not_loaded).