Skip to content
This repository has been archived by the owner on Oct 7, 2023. It is now read-only.

Features

Jump to bottom
Pouriya Jahanbakhsh edited this page Jul 9, 2017 · 6 revisions

Features

  • In server, client and client pool implementation every connection has its own process and Sockerl provides useful and simple API for accessing them and sending data through them or sending Erlang message to them, closing them etc.

  • Every connection process can handle generic calls (requests that have made using gen_server:call/2-3 or gen:call/3-4), generic casts (requests that have made using gen_server:cast/2), generic events (messages in form of {'$gen_event', Event}), disconnecting (when other side closes connection), Erlang system messages, etc.

  • Acceptors and Connectors have been written as Special Erlang process and they are faster than gen_server, gen_fsm, etc.

  • Blocking and non-blocking sockets are supported with doing a few changes in your code.

  • SSL is supported too (you can define your own sockerl_transporter behavior for any protocol like SSL).

  • Connects to multiple addresses and has multiple connections to every address in client pools.

  • Clean and human-understandable error outputs.

  • Accepts standard OTP sys debug options for Acceptors and Connections for generating clean debug output.

  • Simple API for controlling crash of connection processes.

All features not listed here.

  1. Home
  2. Features
  3. Build
  4. Sockerl behavior
  5. Non-blocking server example
  6. Blocking server example
  7. Stand-alone Client connection example
  8. Client connection pool example
Clone this wiki locally