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

dotnet SDK #35

Open
1 task done
jeffdoolittle opened this issue Jul 28, 2023 · 4 comments
Open
1 task done

dotnet SDK #35

jeffdoolittle opened this issue Jul 28, 2023 · 4 comments
Labels
A-Other Area: Other enhancement New feature or request

Comments

@jeffdoolittle
Copy link

Is there an existing proposal for this?

  • I have searched the existing proposals

Is your feature request related to a problem?

No

Describe the solution you'd like

According to the documentation, clients for Java and Python are available, such as the following:

https://github.com/bloomberg/blazingmq-sdk-java

I would be interested in helping contribute to an sdk for dotnet if the project maintainers feel this might be of use to the broader community.

Alternatives you considered

No response

@jeffdoolittle jeffdoolittle added the enhancement New feature or request label Jul 28, 2023
@kaikulimu kaikulimu added the A-Other Area: Other label Jul 28, 2023
@hallfox
Copy link
Collaborator

hallfox commented Jul 28, 2023

Hi @jeffdoolittle, thanks for reaching out. We're excited to see such enthusiasm to support BlazingMQ clients in other languages. As mentioned, we have a Java SDK which is a full implementation of the BlazingMQ C++ client SDKs and we are working on publishing a Python SDK which will use native bindings to the C++ client. I'm not sure which one of these approaches would be most appropriate for a .NET SDK, but if the community wants to support these projects we're happy to provide guidance.

I personally think it would be interesting for this repo to provide a C API which most languages could very easily bind to.

@roblugt
Copy link

roblugt commented Jul 28, 2023

Hi
I wonder if it you are considering publishing a wire-level protocol for BlazingMQ? That would allow native client libraries to be developed by the community, which should offer greater flexibility than building on top of a C API. I am particularly interested in a .Net client, but one that makes use of native asynchronous I/O within .Net would be most appealing.

@quarter-note
Copy link
Contributor

Hi @jeffdoolittle and @roblugt Thanks for your interest in the project! Please see my response in another issue. Thanks!

@quarter-note
Copy link
Contributor

Please see #28 (comment) as well.

@hallfox hallfox mentioned this issue Aug 4, 2023
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Other Area: Other enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants