Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
Should an edge agent get just notification about new messages or should it get forwarded messages directly via WebSocket?
In both cases, the mediator needs to know how to forward an incoming message belonging to the given `verkey`. Should it store into storage for polling or send it (message, or notification message) directly via WebSocket.
How to pass such information?
Architecture refactoring
agent
decorators
modules
basicmessage
connections + trustping
credentials
routing + coordinatemediation + messagepickup
storage
transport
utils
wallet
...
Module structure
api/index
handlers
services
messages
Meeting Notes
...
Future topics
Use record state values that match RFC
Easy for comparison, why not?
Only storing message content (CredentialPreview, PresentationPreview, CredOffer) instead of complete didcomm message?