Skip to content
This repository has been archived by the owner on Dec 22, 2023. It is now read-only.

MQTT Support #52

Closed
Rajan opened this issue Jun 22, 2016 · 4 comments
Closed

MQTT Support #52

Rajan opened this issue Jun 22, 2016 · 4 comments

Comments

@Rajan
Copy link

Rajan commented Jun 22, 2016

Does skygear-server support MQTT protocol or something similar which consumes less battery on a mobile device?

@chpapa
Copy link
Contributor

chpapa commented Jun 22, 2016

@Rajan MQTT support is on our roadmap but our intended design is for some data synchronisation usage on IoT application.

May I learn more about why are you interested in this and what are use cases so maybe we can adjust the roadmap / requirements?

@Rajan
Copy link
Author

Rajan commented Jun 22, 2016

Building mobile chat requires a good low-energy mechanism to send/receive messages. MQTT happens to be that. Even Fb messenger and whatsapp use MQTT as a transport. So, I was assuming that your server/chat development kit would have it as a default!

@chpapa
Copy link
Contributor

chpapa commented Jun 22, 2016

@Rajan interesting. that's something we could consider. However HTTP2 is catching up with its reasonably small footprint, support of persistent connection and more extensible. Some interesting discussion here too: http://timkellogg.me/blog/2015/02/20/can-http2-replace-mqtt

Our core team will look into it and if you're interested to contribute we would be happy to help discuss what are the possible architecture to support more transport protocol on the server.

@royuen royuen added the Ideas label Jun 24, 2016
@royuen royuen removed the Ideas label Aug 29, 2016
@chpapa chpapa added meta and removed question labels Mar 28, 2017
@chpapa
Copy link
Contributor

chpapa commented Mar 28, 2017

Moved to SkygearIO/features#15

@chpapa chpapa closed this as completed Mar 28, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants