-
Notifications
You must be signed in to change notification settings - Fork 72
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
RMQTT Development Direction Discussion #10
Comments
EMQX now is to be solution provider of car connection. 它从开源到商业化的契机是电信测试发现只有他家的性能能扛得住,而且必须以公司的形式才能合作。 如果目标只是做 MQTT 的基础设施,好的教程示例和 benchmark 必不可少。各开源MQTT,也得对比一下。 另外,我也在想这种基础设施的开源,如何能活下去,貌似还是要做好大量宣传,找好客户,做好定位。有人用,有人原因付钱,才可能有迭代下去的动力、资源。当然我也卡在这里了。 |
As a fundamental component of the IoT platform, RMQTT will continue to improve its functionality and documentation. Thank you |
是的,RMQTT的第一目标就是作为MQTT的基础设施,之后会先完善一些文档,准备一些代码样板,比如auth-http-server等。也在考虑简化对ntex-mqtt的依赖。 |
对了,若是有商业用户,麻烦挂一下到 README 里,至少这样别人也才有意愿去试错 |
有道理! |
IoT master is the best fit. rmqtt supports grpc, mqtt and http(s). I am using it on a RPi to control a local network of small IoT devices. The data from the IoT will be stored on the RPi and a Vue web app will control the system. I would like to see a config section for serving http(s) pages using salvo. (BTW salvo is at 0.44.x) |
Thank you for your suggestion. Do you want HTTP API to support HTTP (s)? |
https is secure. I would like to have a web server interface along with having a http-api |
什么时候同步到ntex-mqtt的新版本? |
对ntex-mqtt的改动太大,基本没法简单同步了,现在主要用到的是ntex-mqtt对mqtt的编解码部分,暂时没有同步到最新的必要了。
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月05日 15:13 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [rmqtt/rmqtt] RMQTT Development Direction Discussion (Issue #10) |
什么时候同步到ntex-mqtt的新版本?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
我尝试升级过,还是可以改的,另外现在的n tex-mqtt的websocket example 一直跑不通,不知道你们试过没
|
rmqtt之后的版本会考虑只使用ntex库和ntex-mqtt中的协议部份。ntex-mqtt的websocket没用过,目前rmqtt中的websocket使用的是tokio-tungstenite。
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年09月06日 21:30 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [rmqtt/rmqtt] RMQTT Development Direction Discussion (Issue #10) |
我尝试升级过,还是可以改的,另外现在的mtex-mqtt的websocket example 一直跑不通,不知道你们试过没
对ntex-mqtt的改动太大,基本没法简单同步了,现在主要用到的是ntex-mqtt对mqtt的编解码部分,暂时没有同步到最新的必要了。
---- 回复的原邮件 ----
| 发件人 | @.> |
| 日期 | 2023年09月05日 15:13 |
| 收件人 | @.> |
| 抄送至 | @.>@.> |
| 主题 | Re: [rmqtt/rmqtt] RMQTT Development Direction Discussion (Issue #10) |
什么时候同步到ntex-mqtt的新版本?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
MQTT over QUIC 是否可以考虑增加 |
感谢您对此项目的关注,这是一个非常好的建议,我们将把对 QUIC 的支持加入到开发计划。
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2023年11月08日 09:36 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [rmqtt/rmqtt] RMQTT Development Direction Discussion (Issue #10) |
MQTT over QUIC 是否可以考虑增加
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Out of curiosity, has the development on this stopped? What is the status? Have you guys tried to compile this on a mac m3 (arm64), i'm having some issues trying to compile it. Looks like a really great product! well done! |
Hello, I don’t have a mac m3 environment, so I haven’t tried compiling on it. What compilation problems did you encounter?
…---- Replied Message ----
| From | Anton ***@***.***> |
| Date | 01/19/2024 16:30 |
| To | ***@***.***> |
| Cc | ***@***.***>***@***.***> |
| Subject | Re: [rmqtt/rmqtt] RMQTT Development Direction Discussion (Issue #10) |
Out of curiosity, has the development on this stopped? What is the status?
Have you guys tried to compile this on a mac m3 (arm64), i'm having some issues trying to compile it.
Looks like a really great product! well done!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I think i boiled it down to this: When i try to compile inside of a arm64 container on m3 mac i get:
and if i try to run as a amd64 container using rosetta for emulation i get this:
|
I can compile on the RPi4 ARM64 with no problem |
when i tested it with "cross" without giving target as an argument i got some error saying that "aarch64-apple-darwin" not a target, so there is something else needed to build it on a apple device. |
能支持自身集成kafka么?把所有消息转发到kafka.下游服务器只需要订阅kafka即可,提升吞吐量.emqtx只有企业版有,我是才寻到此处. |
您好,首先感谢您对本项目的关注,此种方式的数据桥接己在计划中,谢谢!
…---- 回复的原邮件 ----
| 发件人 | ***@***.***> |
| 日期 | 2024年07月15日 08:12 |
| 收件人 | ***@***.***> |
| 抄送至 | ***@***.***>***@***.***> |
| 主题 | Re: [rmqtt/rmqtt] RMQTT Development Direction Discussion (Issue #10) |
能支持自身集成kafka么?把所有消息转发到kafka.下游服务器只需要订阅kafka即可,提升吞吐量.emqtx只有企业版有,我是才寻到此处.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
您好,rmqtt 0.6.0已经支持桥接kafka。 |
可否考虑下把web 监测界面的实现换成grafana的 dashboard |
Thank you for your support and attention to RMQTT. For the future development direction of RMQTT, you can put forward valuable suggestions and opinions according to your specific business needs in the process of use.
thank you all
The text was updated successfully, but these errors were encountered: