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

Features

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

Features

  • In server and client 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 process calls handle_call function of your callback module for call requests, calls handle_cast function for cast requests, calls handle_event function for incoming events, calls terminate function for termination, calls timeout function for timeouts, calls srtimeout function for socket-receive-timeouts, etc. Also you don't need to handle system messages.

  • 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).

  • 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.

Clone this wiki locally