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
{{ message }}
Repository navigation
plans for amqp/nats/stan/etc (similar to sdk-go)? #390
Is your feature request related to a problem? Please describe.
The sdk-go project contains protocol implementations for other popular message buses, such as AMQP, NATS/STAN, and Kafka. I would like to see the same protocol layer available in the javascript SDK.
Describe the solution you would like to see
The same interfaces created for Protocol, Consumer, Receiver, Sender, etc, with a client class that leverages the interfaces. Bonus points if someone can write one or more of the protocol implementations for AMQP or Kafka.
Additional context
I'm working on a project that has a mix of typescript/javascript and golang based services using a mix of message transports. It would be great to standardize on something like cloudevents for the message format.
Hi @justinrush - yes, we would definitely like to support all of the protocols that have a specification. There is no active work toward these goals at the moment, but we welcome contributions if you find yourself interested in that.
Hi @Alexis01 the situation is about the same as it was this spring. There is no active work towards these goals at the moment, but we welcome contributions if you find yourself interested in that task.
@lance@justinrush@Alexis01 My team wants to use CoudEvents for our JS services, but currently, for transport, we use only Kafka. I made cloudevents-kafka package as Kafka transport extension for the main cloudevents library, with all features which need for us right now.
I do not have enough time to work on PR in this repository, but anyone who wants can use my package or copy it as PR in this repo.
I think we can probably just close this, period. It's pretty broad and includes more than just transport implementations. The original ask is for all of the same interfaces here as in the Go SDK. But this implementation comes at it from a completely different perspective - not the least of which is the fact that Javascript is 'bring-your-own-transport-implementation' and Go just uses the built in HTTP under the hood to provide the implementation directly.
Activity
lance commentedon Apr 1, 2021
Hi @justinrush - yes, we would definitely like to support all of the protocols that have a specification. There is no active work toward these goals at the moment, but we welcome contributions if you find yourself interested in that.
github-actions commentedon May 2, 2021
This issue is stale because it has been open 30 days with no activity.
Alexis01 commentedon Oct 21, 2021
what about this request?
lance commentedon Oct 21, 2021
Hi @Alexis01 the situation is about the same as it was this spring. There is no active work towards these goals at the moment, but we welcome contributions if you find yourself interested in that task.
github-actions commentedon Nov 22, 2021
This issue is stale because it has been open 30 days with no activity.
LeoVS09 commentedon Dec 19, 2021
@lance @justinrush @Alexis01 My team wants to use CoudEvents for our JS services, but currently, for transport, we use only Kafka. I made cloudevents-kafka package as Kafka transport extension for the main
cloudeventslibrary, with all features which need for us right now.I do not have enough time to work on PR in this repository, but anyone who wants can use my package or copy it as PR in this repo.
feat: add support for kafka transport
feat: add support for kafka transport
feat: add support for kafka transport
feat: add support for kafka transport
feat: add support for kafka transport (#455)
lholmquist commentedon Jan 10, 2022
once we do a new release with. #455 , can this be closed, or should we keep it open until those other protocols are dealt with?
lance commentedon Jan 11, 2022
I think we can probably just close this, period. It's pretty broad and includes more than just transport implementations. The original ask is for all of the same interfaces here as in the Go SDK. But this implementation comes at it from a completely different perspective - not the least of which is the fact that Javascript is 'bring-your-own-transport-implementation' and Go just uses the built in HTTP under the hood to provide the implementation directly.
lholmquist commentedon Jan 11, 2022
closing, and if we need to re-open we can