You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need the dido library to raise an event at the moment when a DID exchange results in a connection being established. This needs to happen both for the pico receiving the invitation and the one that generated it. An application ruleset (that uses io.picolabs.did-o as a module) would react to this event and maintain a list of connections, on top of the didMap function that the did-o ruleset already provides (the app ruleset is not part of what is asked for here, but is the rationale).
Event attributes need to include
the role of this pico (whether "inviter" or "invitee")
the label from the invitation
the DID that this pico is going to use going forward
the DID that the other pico has communicated for use going forward
anything else that is available and might be useful
The text was updated successfully, but these errors were encountered:
The dido:invitation_accepted event could then be selected by a rule (in another ruleset) that could obtain
the role would be "invitee"
the label would be event:attrs{["invite","label"]}
the DID for this pico would be event:attrs{"my_did"}
the DID for the other pico would be event:attrs{["invite","from"]}
anything else out of event:attrs{"invite"}, such as perhaps the time when the invitation was created (computed as time:new(event:attrs{["invite","created_time"]}*1000))
We need the
dido
library to raise an event at the moment when a DID exchange results in a connection being established. This needs to happen both for the pico receiving the invitation and the one that generated it. An application ruleset (that usesio.picolabs.did-o
as a module) would react to this event and maintain a list of connections, on top of thedidMap
function that the did-o ruleset already provides (the app ruleset is not part of what is asked for here, but is the rationale).Event attributes need to include
The text was updated successfully, but these errors were encountered: