Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Remember the Hyperledger Code of Conduct

Anti-Trust Policy:

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.

Attendees

Resources

Status updates

Agenda

  • Record the meeting
  • Moving to OWF
  • Separating the storage layer
    • Storing messages? All state should be derived from message exchange
      • User chooses whether to store the messages, but user needs to provide the current state of the protocol
    • Goal from Timo: More control over the database entities, how state is persisted. 
    • Built in storage useful in a lot of cases as well
    • Discuss next time: current storage model
  • DIDComm v2
  • 0.5.0 release
  • Keeping http socket open, when using implicit invitations
    • delay the closing of the http session?
    • Have a interface to override session closing handling? If not registered it will auto close if no response internally. Otherwise you get control over it
    • Add option to auto accept requests to implicit invitations for certain dids?
      • DidRecord.metadata.allowImplicitInvitations = true
      • config: { autoAcceptImplicitInvitationsForDids: ["did:web:mediator.animo.id"] }
  • Support ~timing decorator natively in AFJ

Meeting Notes



Recording / Slides


Future topics

Future Topics:


  • It would be good to discuss OCA implementation in AFJ and in Aries Bifold and where should be a boundary between the two in this feature.
  • Extracting parts of AFJ into generic libraries
  • Cheqd integration (Daev Mithran )
  • AFJ Interop tests not running


  • No labels