Karl Morrison

@jruizaranguren Slightly different scenarios. The one in the MQTT has a broker. Client Broker Client. I'm specifically interested in the Client Client scenario, e.g. for WebSocket connections from web clients...

Me and a co-worker had a chat and we would like to support several different actions on a "channel". for channel `mychannel/{myChannelId}` in our case we would like a publish/subscribe...

@jonaslagoni As stated every protocol implements their own terminology for these things so I guess AsyncAPI will either have to add ALL of these terms to make everyone happy or...

Would like to say we have forked 4 of the repos from https://github.com/asyncapi and have implemented the following: command: ... request: ... response: ... unsubscribe: ... unsubscribe ack: ... subscribe:...

@fmvilas > Interesting. What's the meaning of each of them? We can probably incorporate them into future versions. All acks work the same: this is sent to the sender to...

@kvaleev When I think of events I think that an event is broadcast meaning anyone who listens will receive it, and it feels like subscribe/publish pattern solves this? You are...

@kvaleev Now when I think of it event could be added, which as the gif animation explains, would be the result of a publish message type coming into the server.

@nikhilk If you do update the documentation I'll go straight over it and some cases make a pull request. I like dumbing down these kinds of things and making things...

@nikhilk The other bug was filed under due to me following the new instructions. You explain everything needed to know as a Javascript developer on Linux. I like that you...

Thanks, that fixed the issue!