Hi Yun,
Yes, you're correct but with one additional point. Your special client
isn't just for saving messages to the database, it's for the server
side application processing - i.e. turning it into a chat application
rather than simply clients connected to an MQTT broker. It would also
be doing th
for the "client" you are talking about here, just want to make sure i
understand correctly:
what i should do is:
1. just run a *regular *broker as the original mosquitto broker on the
server side.* I should not modify it at all;*
2. meanwhile, i should implement a *special client* on the *server
Thank you a lot Roger! really great suggestions on how to do it.
for the server side, i think my challenge will be how to add the database
storage functionality while:
- making it still be able to easily compatible with future version of
mosquitto and;
- keeping it easier to support my o
Hi,
>> 3. for the iPhone wrapper of the mosquitto client, I checked Marquette , is
>> this wrapper compatible with the latest version of Mosquitto 1.0.2
>
> From what I can see, the last commit to Marquette was 8 months ago, so
> unfortunately no it isn't compatible with 1.0.2.
I'm sure that Nick
Hi Yun,
> 1. what's the best practice to connect Mosquitto broker with the MySQL to
> make sure: all messages are stored in the database? Ideally, all message
> sent to server should be stored in the db before they are distributed, to
> ensure the data security.
At the moment you have to write an
Hi,
I knew that Facebook used mosquitto in their messenger app on iPhone. and
it worked pretty well. Here is what they say:
http://www.facebook.com/notes/facebook-engineering/building-facebook-messenger/10150259350998920
I am considering using Mosquitto to implement a chat/messaging service for
m
6 matches
Mail list logo