esubscribe

Erlang library for distributed term subscriptions.

I tried to keep API as simple as possible.

I appreciate any pull requests for bug fixing, tests or extending the functionality.

API

esubscribe:start_link()

Call it from an OTP supervisor as a permanent worker. Example:

MySubsriptionsServer = #{
    id=>esubscribe,
    start=>{esubscribe,start_link,[]},
    restart=>permanent,
    shutdown=> <It's up to you>
    type=>worker,
    modules=>[esubscribe]
},

Ok now you are ready for subscriptions. If you need distributed subscriptions do the same
at your other nodes.

If you want to subscribe on any erlang term call:

ok = esubscribe:subscribe(Term, PID)

Term is any erlang term
PID is self() ??? Why I need to pass my PID, take it as self(). 
Yes you can subscribe another process.

If you want to subscribe on any erlang term on several nodes call:

{YesNodes,NoNodes} =  
    esubscribe:subscribe(Term, PID, Nodes)

Nodes is a list of nodes where you want subscribe

[{Node1,ok},{Node2,ok}|_AndSoOn] = YesNodes are the nodes from Nodes where you were susccessful

[{Node1,Reason1},{Node2,Reason2}|_AndSoOn] = NoNodes are the nodes where you failed with reasons

If you want to notify on any term call:

ok | {error, not_available} = esubscribe:notify( Term, Action )

Term is any erlang term
Action is also any erlang term

You can get your notification in 3 ways:
1 -> call 
    [{Action1,Node1,Actor1},{Action2,Node2,Actor2}|_AndSoOn] = esubscribe:lookup( Term ) 
2 -> call
    wait( Term, Timeout ) the format of the return is the same as for case 1
3 -> 
    Classic erlang:
    receive
        {'$esubscription', Term, Action, Node, Actor}

that's it.

BUILD

Add it as a dependency to your application and you are ready (I use rebar3)
{deps, [
    ......
    {esubscribe, {git, "git@github.com:vzroman/esubscribe.git", {branch, "main"}}}
]}.

TODO

Tests!!!