Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(*): Updates messaging to support request-reply #21

Closed

Commits on Feb 27, 2024

  1. feat(*): Updates messaging to support request-reply

    This makes several updates to the messaging interface. Initially the
    README said that this wasn't going to support request/reply, but based
    on my reading of the Kafka, NATS, MQTT, and SQS APIs, this is a fairly
    common pattern. Another piece of evidence here is what I've seen as a
    wasmCloud maintainer from our users. Request/reply is one of the more
    common things we see with a messaging service. Please note that this
    doesn't _require_ the use of a reply-to topic, just exposes it for use.
    
    I also did a few other changes here. First is that I added the topic to
    the message. This was common across all systems and is often used by code
    to select the appropriate logic to perform. I also removed the format
    field as this didn't seem to be a common parameter across various services.
    We could definitely add a content-type member to this record in the future
    if needed, but I think much of that can be passed via the metadata field.
    
    There are other things I might suggest some changes to, but I want to think
    on them some more and open some issues to discuss them first
    
    Signed-off-by: Taylor Thomas <taylor@cosmonic.com>
    thomastaylor312 committed Feb 27, 2024
    Configuration menu
    Copy the full SHA
    6231f8a View commit details
    Browse the repository at this point in the history