Elixium Core v0.6.3 Elixium.Store.Oracle View Source

Responsible for reading and writing to a given store on behalf of other processes. This fixes the issue with LevelDB not allowing multiple processes read / write to a store at the same time.

Link to this section Summary

Functions

child_spec(arg)

Returns a specification to start this module under a supervisor

init(store_ref)

Invoked when the server is started. start_link/3 or start/3 will block until it returns

inquire(pid, options)

Call a method on the store module of a given oracle. Takes in a reference to a started oracle process, and a tuple with the method name, and a list of options to pass to the method. E.g. Oracle.inquire(oracle, {:load_known_peers, []})

start_link(store)

Start an oracle to interface with a given module. Running an oracle with a store will cause it to lock down the store, and no other process will be able to communicate with it until the oracle has died

Link to this section Functions

child_spec(arg)

Returns a specification to start this module under a supervisor.

See Supervisor.

init(store_ref)

Invoked when the server is started. start_link/3 or start/3 will block until it returns.

args is the argument term (second argument) passed to start_link/3.

Returning {:ok, state} will cause start_link/3 to return {:ok, pid} and the process to enter its loop.

Returning {:ok, state, timeout} is similar to {:ok, state} except handle_info(:timeout, state) will be called after timeout milliseconds if no messages are received within the timeout.

Returning {:ok, state, :hibernate} is similar to {:ok, state} except the process is hibernated before entering the loop. See c:handle_call/3 for more information on hibernation.

Returning {:ok, state, {:continue, continue}} is similar to {:ok, state} except that immediately after entering the loop the c:handle_continue/2 callback will be invoked with the value continue as first argument.

Returning :ignore will cause start_link/3 to return :ignore and the process will exit normally without entering the loop or calling c:terminate/2. If used when part of a supervision tree the parent supervisor will not fail to start nor immediately try to restart the GenServer. The remainder of the supervision tree will be started and so the GenServer should not be required by other processes. It can be started later with Supervisor.restart_child/2 as the child specification is saved in the parent supervisor. The main use cases for this are:

The GenServer is disabled by configuration but might be enabled later.
An error occurred and it will be handled by a different mechanism than the Supervisor. Likely this approach involves calling Supervisor.restart_child/2 after a delay to attempt a restart.

Returning {:stop, reason} will cause start_link/3 to return {:error, reason} and the process to exit with reason reason without entering the loop or calling c:terminate/2.

Callback implementation for GenServer.init/1.

inquire(pid, options)

inquire(pid(), tuple()) :: any()

start_link(store)

start_link(atom()) :: {:ok, pid()} | {:error, String.t()}