# Blanket covers your ETS tables

If you use ETS with Elixir and Erlang, you know that the table is bound to a process, and if this process chrashes, the tables vanishes. All data is lost.

The simplest thing to do is to start a process responsible for owning the table, and do all actual table operation on another process. But this requires coodination between the two process, public named tables with an unique name. Sometimes, you need several private or protected unnamed tables.

Read a thorough explanation of theese problems and a simple solution to them on Steve Vinoski's Blog here : [Don't Lose Your ets Tables](

You can also look an erlang implementation of the solution [on github](

## Installation

Just define	the `:blanket` dependency in your project's `mix.exs`.
  defp deps do
    [{:blanket, "~> 0.2.0"}]

## Documentation

The documentation can be found on [Hex Docs](

## Example

This is a simple example generic table owner server using `Process.register` to
registerits name. Just check out the comments.

Others strategies for identifying processes are available.

defmodule MyApp.TableTop do
  use GenServer
  use Blanket

  def start_link(name) do
    # 1. Define a table as you would do with ETS. Here is the equivalent of
    #, [:set, :protected])
    table_def = {:users, [:set, :protected]}
    # 2. Create a new Blanket process to be the table heir, passing a name for
    # the table owner process. The table is created.
    {:ok, _} =, name, table_def)
    # 3. Start your table owner process.
    GenServer.start_link(__MODULE__, [name])

  # ...

  def init([name]) do
    # 1. The table owner registers its name to be found by the table heir. Any
    # registration system is possible, would it be Process.register, or gproc,
    # global, a custom pid store …
    Process.register(self, name)
    # 2. Call Blanket.receive_table to be given the table on fresh start and
    # each time you restart. You must register *before* so the heir can find
    # you.
    {:ok, tab} = Blanket.receive_table
    # 3. You now own the table and can use it
    {:ok, tab}



## Identifying processes

The previous example uses `Process.register` to register its name. The heir is
given the owner's module and its name, and can find the owner's pid by calling
`module.get_owner_pid(name)`. This function is defined in your module by calling `use Blanket` in your module definition.

This is equivalent to the following function :

  def get_owner_pid(name) do

If you wish to use a different mechanism, *e.g.* [gproc](, you must define your own `get_owner_pid` function :

  def get_owner_pid(name) do
    :gproc.whereis({:n, :l, name})

You can now register your process with gproc :

  def init([name]) do
    :gproc.reg({:n, :l, name})

Remember to always register your process before calling Blanket.`receive_table`.

## Table initialisation

`` accepts an anonymous function as its fourth argument. If present, this function will be passed the ETS table as its sole argument. The function is evaluated as the table owner so you can act on private tables.

The function *must* return `:ok`. Any other value will be returned as an error tuple after the table have been deleted.

## Todo

 - abandon_table