B4J Video Conference / Video Streaming (RTSP H.264) / and webRTC

[Star-Dust]

What are the advantages of creating an MQTT server instead of one based on websockets?

It's a bit annoying to see your progress... without being able to have the source code (right @Xfood? ? )

Two advantages

• Creating a server with the MQTT library I make it with 3 lines of code and that's it.
• The next job I will start I have to use MQTT and so I get experience

 

[Star-Dust]

I agree, I hope that as soon as the project completes it makes the source available

Sorry, no source

 

[Xfood]

Sorry, no source

not even for sale?

 

[Star-Dust]

last update

 

[Xfood]

and I haven't had a nice new source for a while, I'm in a withdrawal crisis ..???

 

[Magma]

What are the advantages of creating an MQTT server instead of one based on websockets?

From an IoT perspective, MQTT is arguably the better option of the two. This is because Websocket isn't extremely well suited to IoT devices. It was initially designed for the full-duplex communication channel between browsers and servers

A Google search...

Sometimes is 4x times faster...

And ofcourse using it with b4x is super easy...

 

[Star-Dust]

not even for sale?

No, because despite having created the library that does almost everything automatically, it is not easy to make it work and understand the mechanism. I want to avoid them pestering me with questions while I work because they can't get it to work.

 

[Xfood]

No, because despite having created the library that does almost everything automatically, it is not easy to make it work and understand the mechanism. I want to avoid them pestering me with questions while I work because they can't get it to work.

ok, for me there is no problem, you know I never bother you, you can send me the source as soon as you complete it. Thank you.?????

 

[Star-Dust]

I know the opposite. However the answer is no.

 

[LucaMs]

This is because Websocket isn't extremely well suited to IoT devices.

Why?

 

[Magma]

Why?

Google saying..

Other sites like hivemq... saying that is different layer... so works 4x times faster..

 

[Star-Dust]

Why?

On the forum you will find many explanations of Erel on this.
But quickly I can tell you that it is a very simple and fast protocol that has been designed for iot devices, that is, the transmission has a low consumption of Bytes and a great reliability. Undeliverable messages remain on hold and there are three levels of security for message delivery.

Unlike the WebSocket which is 'one to many', MQTT works as 'many to many', similar to a chat, every message sent by a client is automatically forwarded to all those listening on the channel.

Then it is clear that with the appropriate code the WebSocket you can make it work as many to many and also MQTT you can make it work as one to many.

 

[LucaMs]

Unlike the WebSocket which is 'one to many', MQTT works as 'many to many', similar to a chat, every message sent by a client is automatically forwarded to all those listening on the channel.

This can only make the server slower rather than faster.
If the server sends all the messages it receives and passes them on to all the connected clients (then each client must read the message and check if it is useful for it) it doesn't seem like an advantage, far from it.

In my opinion you have more control with a websocket server and no downside.
Implementation with B4J is also just as simple.

Creating a server with the MQTT library I make it with 3 lines of code and that's it.

 

[Star-Dust]

This can only make the server slower rather than faster.
If the server sends all the messages it receives and passes them on to all the connected clients (then each client must read the message and check if it is useful for it) it doesn't seem like an advantage, far from it.

In my opinion you have more control with a websocket server and no downside.
Implementation with B4J is also just as simple.

It depends on the needs. However, on mqtt auction write on specific channels and receive them only some or only one. However, I need everyone to receive.

 

[Magma]

This can only make the server slower rather than faster.
If the server sends all the messages it receives and passes them on to all the connected clients (then each client must read the message and check if it is useful for it) it doesn't seem like an advantage, far from it.

...the server not sends... just open and wait for client (that not means... all client will the same time... but the message will wait - that is good)... it is different layer of TCP and not works the same with http... MQTT brokers have different philosophy... I agree if they are too many clients will be slow... (it depends to the type of app)...

I believe MQTT can help in many APPs...

 

[LucaMs]

Well I haven't deepened my knowledge of MQTT.
It seems to me that you have more control over a websocket server, but I'm not unlikely to be wrong.

 

[Magma]

@LucaMs We aren't masters... (let me think.... may be I am...) you must try it... I have to say that many apps... working better with MQTT... is not the solution to everything but is a good and secure system... (actually can be secure... if ssl exists and some kind of credentials)

some nice words for mqtt (pros and cons):

The Pros and Cons of Using MQTT Protocol in IoT

Are you considering using MQTT as a data connection IoT protocol? Before you do, check out our pros and cons and decide if it’s right for your project.

www.nabto.com

ps: If you tried once ... you will "love" it

 

[LucaMs]

ps: If you tried once ... you will "love" it

It is more likely that if you try a b4j websocket server you will fall in love with it

 

[Magma]

It is more likely that if you try a b4j websocket server you will fall in love with it

but ofcourse I am loving it too ...but I feel that it hates me

 

[Star-Dust]

First attempts at Directing for H.264 video broadcasts