View Source PropertyTable (property_table v0.2.0)

In-memory key-value store with subscriptions

PropertyTable makes it easy to set up a key-value store where users can subscribe to changes based on patterns. PropertyTable refers to keys as properties. Properties have values and are timestamped as to when they received that value. Subscriptions make this library feel similar to Publish-Subscribe. Events, though, are only for changes to properties.

PropertyTable is useful when you want to expose a decent amount of state and let consumers pick and choose what parts interest them.

PropertyTable consumers express their interest in properties using "patterns". A pattern could be as simple as the property of interest or it could contain wildcards. This allows one to create hierarchical key-value stores, map-based stores, or just simple key-value stores with notifications.

PropertyTable is not persistent. Keys and values are backed by ETS.

Link to this section Summary

Types

option()

PropertyTable configuration options

pattern()

property()

Properties

property_value()

table_id()

A table_id identifies a group of properties

value()

Functions

child_spec(opts)

Returns a specification to start a property_table under a supervisor. See Supervisor.

delete(table, property)

Delete the specified property

delete_matches(table, pattern)

Delete all properties that match a pattern

fetch_with_timestamp(table, property)

Fetch a property with the time that it was set

get(table, property, default \\ nil)

Get the current value of a property

get_all(table)

Get all properties

match(table, pattern)

Get a list of all properties matching the specified property pattern

put(table, property, value)

Update a property and notify listeners

put_many(table, properties)

Update many properties

start_link(options)

Start a PropertyTable's supervision tree

subscribe(table, pattern)

Subscribe to receive events

unsubscribe(table, pattern)

Stop subscribing to a property

Link to this section Types

option()

@type option() ::
  {:name, table_id()}
  | {:properties, [property_value()]}
  | {:tuple_events, boolean()}

PropertyTable configuration options

See start_link/2 for usage.

pattern()

@type pattern() :: any()

property()

@type property() :: any()

Properties

property_value()

@type property_value() :: {property(), value()}

table_id()

@type table_id() :: atom()

A table_id identifies a group of properties

value()

@type value() :: any()

Link to this section Functions

child_spec(opts)

@spec child_spec(keyword()) :: Supervisor.child_spec()

Returns a specification to start a property_table under a supervisor. See Supervisor.

delete(table, property)

@spec delete(table_id(), property()) :: :ok

Delete the specified property

delete_matches(table, pattern)

@spec delete_matches(table_id(), pattern()) :: :ok

Delete all properties that match a pattern

fetch_with_timestamp(table, property)

@spec fetch_with_timestamp(table_id(), property()) ::
  {:ok, value(), integer()} | :error

Fetch a property with the time that it was set

Timestamps come from System.monotonic_time()

get(table, property, default \\ nil)

@spec get(table_id(), property(), value()) :: value()

Get the current value of a property

get_all(table)

@spec get_all(table_id()) :: [{property(), value()}]

Get all properties

This function might return a really long list so it's mainly intended for debug or convenience when you know that the table only contains a few properties.

match(table, pattern)

@spec match(table_id(), pattern()) :: [{property(), value()}]

Get a list of all properties matching the specified property pattern

put(table, property, value)

@spec put(table_id(), property(), value()) :: :ok

Update a property and notify listeners

put_many(table, properties)

@spec put_many(table_id(), [{property(), value()}]) :: :ok

Update many properties

This is similar to calling put/3 several times in a row, but atomically. It is also slightly more efficient when updating more than one property.

start_link(options)

@spec start_link([option()]) :: Supervisor.on_start()

Start a PropertyTable's supervision tree

To create a PropertyTable for your application or library, add the following child_spec to one of your supervision trees:

{PropertyTable, name: MyTableName}

The :name option is required. All calls to PropertyTable will need to know it and the process will be registered under than name so be sure it's unique.

Additional options are:

:properties - a list of {property, value} tuples to initially populate the PropertyTable
:matcher - set the format for how properties and how they should be matched for triggering events. See PropertyTable.Matcher.
:tuple_events - set to true for change events to be in the old tuple format. This is not recommended for new code and hopefully will be removed in the future.

unsubscribe(table, pattern)

@spec unsubscribe(table_id(), pattern()) :: :ok

Stop subscribing to a property

Settings View Source PropertyTable (property_table v0.2.0)

Link to this section Summary

Types

Functions

Link to this section Types

option()

pattern()

property()

property_value()

table_id()

value()

Link to this section Functions

child_spec(opts)

delete(table, property)

delete_matches(table, pattern)

fetch_with_timestamp(table, property)

get(table, property, default \\ nil)

get_all(table)

match(table, pattern)

put(table, property, value)

put_many(table, properties)

start_link(options)

subscribe(table, pattern)

unsubscribe(table, pattern)

View Source PropertyTable (property_table v0.2.0)