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
In certain situations we would like to publish messages over FiksIO, without handling incoming messages. For example incoming messages from our internal message broker. In those cases we do not need the AMQP connection or the resources required to connect to it (we keep the sensitive information like certificates and passwords in an external vault) as we only want to publish and not consume.
I looked into using your FiksIOSender package for this, but this requires encrypting the payload with the recipient's public key and then provide the sender client with the encrypted stream.
The FiksIOClient handles this internally and exposes methods for supplying a list of unencrypted streams, which is much more comfortable to work with as it doesn't require knowledge about the asice containers.
In certain situations we would like to publish messages over FiksIO, without handling incoming messages. For example incoming messages from our internal message broker. In those cases we do not need the AMQP connection or the resources required to connect to it (we keep the sensitive information like certificates and passwords in an external vault) as we only want to publish and not consume.
I looked into using your FiksIOSender package for this, but this requires encrypting the payload with the recipient's public key and then provide the sender client with the encrypted stream.
The FiksIOClient handles this internally and exposes methods for supplying a list of unencrypted streams, which is much more comfortable to work with as it doesn't require knowledge about the asice containers.
Could you consider moving the logic contained in the FiksIOClient to the FiksIOSender instead?
The text was updated successfully, but these errors were encountered: