privatesky / opendsu

OpenDSU SDK

OpenDSU SDK as API spaces

http :Http client APIs

crypto :Recommended Crypto APIs

anchoring :Anchoring Services

bricking :Bricks Storages

keyssi :KeySSI manipulation

resolver :Obtain DSU Representations using a resolver

handlers :DSU Handlers

notifications :Notifications based on KeySSIs

mq :Working with Message Queues based on KeySSIs

dc :DSU Channels and messaging based on KeySSIs and DSUs

sc :Security Context

bdns :Handling Blockchain Domain Name Service

choreographies :OpenDSU APIs and choreographies

dt :Handling the creation/manipulation of DSU Types

opendsu's Issues

sc.on("initialized", handler) behaviour

sc.on("initialised", handler) should trigger handler even if security context is already initialized? Now, it is not.

abc

this.didDocument.readMessage(handler) error handling discussion

I have the following code

listenForMessages(callback) {
         this.didDocument.readMessage((err, decryptedMessage) => {
            if (err) {
                console.error(err);
            } else{
               callback(err, decryptedMessage);
            }
             this.listenForMessages(callback);
        });
}

If I refresh the browser while I have a pending request (from the readMessage call) an error will be thrown and it will enter in an infinite loop of throwing fetch errors like the following:

forcing me to return if an error occurs and to not call again the this.didDocument.readMessage method

I'm not sure that this kind of errors, connection errors should be bubbled up to this, or maybe them should be wrapped in error types.

Export Mixins so new KeySSI, DIDs, etc can be implemented from outside OpenDSU