Hello everyone. Welcome to the section number eight where we're
going to talk about the cope, which is also another application layer
communication protocol same like mqtt.
So this is video number 8.1 and we're going to talk about what
is scope and how it works. It's architecture and
it's feature. So guys, let's get started with that.
So firstly we will know its abbreviation which is constrained application
protocol and it's a lightweight
application protocol just like mqtt but it
works in a different mod like request and
response communication protocol which is based on
the HTTP. It is used for
MTM communication runs over udp/ip stack
instead of tcp/ip Stack design for
interpretability with the web mqtt
doesn't interoperability works
with the existing web Technologies. So
copious designed to give a better
user experience with the existing web Technologies designed for
remote connections where they have a limited bandwidth
same like mqtt.
And if we talk about the features then mqtt and
core feature resembles with each other just like lightweight and
efficient but one is a different as the asynchronous message
exchange nor the instant communication
because mqtt is an instant
and same like mqtt it scales
up to the million of devices.
And the major difference is mqtt used
topic based but Cove uses URI and
the content type sport which is not available
in mqtt. So both are different from that perspective.
And this is the main perspective which
makes them different from each other security enable
same like an mqtt but the web interoperability is
available in this program communication protocol and
not available in mqtt.
So now it's time to talk about how it works.
so
here is our server for
Server. Okay, and if we see that URL it's
same like HTTP, but here we're mentioning
the cop instead of HTTP. And the
rest of things are the same as we
have a HTTP request. So how it's working
is there are cope client like one and this is a Coke line
2 server is sending the get request
to the client.
and then the client is sending back the
response in the
Cove format and this is the second device service
sending get request
and the device is sending response to the server. So
in this way, the things are
work and that's why this is the asynchronous not a synchronous.
So if we talk about the application same like mqtt, we
have a lot of applications where we
can use that and specifically if you want to
make your applications interoperative with
the web. Then the cope is a good choice and
it's performance is a little
bit higher due to asynchronous communication and
I also saves battery as compared to the mqtt.
So there are different scenarios like remote assist
tracking for example if you want to track
The assets where you want to get the
location then go up is a good choice and smart
building small Healthcare smart Agriculture and
the industrial iot. So it's all
up to you that which communication protocol
either mqtt https HTTP
or Coke. I totally
depends on your scenarios what type of application protocol you
are using because it depends on your requirements and
your infrastructure your devices capabilities and
main thing is how you
want to fight the data from your devices. So guys
do some research and share. Where is
mqtt better as computer cope. And where
is cope is better as compared to mktt.
So guys see you in our next video. We are going to work on
the cope client and
see you next video. Have a good day. Bye.