generic-linked-in-driver | generic non-blocking

The generic linked-in driver can be used with plain Erlang or with any OTP application. The project itself is compiled using Rebar, so in order to play with the example driver, just cd into the root directory and make the project. Then go to the ebin directory and invoke the erl shell:. The stats/1 function returns the number of calls to the driver and the invoked worker thread. If you start the virtual machine with erl, these numbers will always be the same. This is because the request is processed synchronously, as no asynchronous worker threads are present. If you start the virtual machine with erl +A 4, and thus four worker threads, you will begin to see a difference. If you want to use the generic linked-in driver to create your own specific driver, you basically have two options: using the linked-in driver as a dependency or as a copy.