WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.500 --> 00:00:10.900
Hello everyone. Welcome back to the video number 8.3 where

1
00:00:10.900 --> 00:00:13.200
 we're going to test the cope client and

2
00:00:13.200 --> 00:00:16.000
 the cope device server. So here is the

3
00:00:16.300 --> 00:00:20.100
 cope Jason client that I have created which is

4
00:00:20.100 --> 00:00:23.800
 inherited from the json.js where

5
00:00:23.800 --> 00:00:26.400
 this Jason rjs have both client in

6
00:00:26.400 --> 00:00:29.500
 the server, but I just created that client because we already have

7
00:00:29.500 --> 00:00:30.500
 a device server.

8
00:00:31.200 --> 00:00:31.500
so

9
00:00:33.600 --> 00:00:36.400
In the previous video. I told you that a device

10
00:00:36.400 --> 00:00:39.000
 service capable to respond for the three type of

11
00:00:39.600 --> 00:00:42.600
 request aqy temperature and the humidity and

12
00:00:42.600 --> 00:00:45.800
 in this terminal the server has been already running

13
00:00:45.800 --> 00:00:48.500
 in the background on the power 5683. So

14
00:00:48.500 --> 00:00:52.900
 now it's time to test with the client. So here I just okay.

15
00:00:51.900 --> 00:00:54.400
 Let's see about the code.

16
00:00:54.400 --> 00:00:55.000
 Here we have

17
00:00:56.500 --> 00:00:59.600
Required the core library and the P1 and

18
00:00:59.600 --> 00:01:02.400
 here we are creating the request of that

19
00:01:02.400 --> 00:01:05.700
 request. The URL is temperature. It's less

20
00:01:05.700 --> 00:01:08.600
 temperature that we want to fetch from the device server and

21
00:01:08.600 --> 00:01:11.800
 we accept the application slash Json format

22
00:01:11.800 --> 00:01:14.100
 for the data. And this is

23
00:01:14.100 --> 00:01:18.300
 the response code that we will receive from the server and

24
00:01:17.300 --> 00:01:20.600
 here is the Json response that

25
00:01:20.600 --> 00:01:21.900
 we're going to display here.

26
00:01:22.500 --> 00:01:26.400
So let's call that note the

27
00:01:25.400 --> 00:01:27.000
 node.

28
00:01:28.700 --> 00:01:31.400
For json.js you see here

29
00:01:31.400 --> 00:01:34.400
 that we have requested. The temperature here is

30
00:01:34.400 --> 00:01:37.400
 the response code 2.05 and here's the

31
00:01:37.400 --> 00:01:41.100
 data injection format temperature column 31 and

32
00:01:40.100 --> 00:01:44.100
 server is displaying that device or

33
00:01:43.100 --> 00:01:47.000
 you can say that client has requested slash temperature.

34
00:01:46.700 --> 00:01:49.500
 Okay. Now again, we

35
00:01:49.500 --> 00:01:52.500
 will have the temperature and the random method return

36
00:01:52.500 --> 00:01:55.300
 as a different value 17 and we are also

37
00:01:55.300 --> 00:01:58.600
 watching all the requests that voiceover has

38
00:01:58.600 --> 00:01:59.000
 been receiving

39
00:01:59.800 --> 00:02:02.200
from The Cove client. Okay now it's time to

40
00:02:03.400 --> 00:02:04.800
try humidity.

41
00:02:08.500 --> 00:02:11.800
And you will see the value 49 humidity and

42
00:02:11.800 --> 00:02:12.300
 again.

43
00:02:13.200 --> 00:02:14.800
87 now

44
00:02:15.500 --> 00:02:16.100
these are the

45
00:02:17.100 --> 00:02:20.300
two requests for the humidity and the tool request for the temperature

46
00:02:21.200 --> 00:02:23.800
and it's time for aqi.

47
00:02:27.800 --> 00:02:28.400
You see here.

48
00:02:29.600 --> 00:02:32.700
Every time values has been changing and these are the requests. So

49
00:02:32.700 --> 00:02:35.200
 guys, this is the example where we have

50
00:02:35.200 --> 00:02:38.700
 just created a device server. And this is the core client. You

51
00:02:38.700 --> 00:02:41.300
 can consider it. This is a device and this is the web

52
00:02:41.300 --> 00:02:44.500
 based application which is getting the data from the

53
00:02:44.500 --> 00:02:46.700
 device over directly. Okay?

54
00:02:47.600 --> 00:02:50.500
but this is for the testing purpose but in the real cases,

55
00:02:50.500 --> 00:02:53.200
 we need a Corps server where all the

56
00:02:54.500 --> 00:02:57.300
because we are unable to assign a live web

57
00:02:57.300 --> 00:03:00.600
 address to each device because already we have ipv4 shortage

58
00:03:00.600 --> 00:03:03.100
 and it's difficult to

59
00:03:03.100 --> 00:03:06.900
 assign a several IP address. So the server is required and

60
00:03:06.900 --> 00:03:09.800
 board devices and clients will

61
00:03:09.800 --> 00:03:12.000
 interact with each other via the

62
00:03:12.600 --> 00:03:15.400
curb server. So here are the complete list

63
00:03:15.400 --> 00:03:18.600
 of all the stuff in Java and

64
00:03:18.600 --> 00:03:20.900
 python C++. For example if you want to

65
00:03:23.800 --> 00:03:27.000
Deploy, a cop server or cop client on the Arduino devices

66
00:03:26.600 --> 00:03:29.100
 are on a Raspberry Pi then there are

67
00:03:29.100 --> 00:03:32.800
 different libraries which support pythancy plus plus even

68
00:03:32.800 --> 00:03:34.500
 dotnet is also available.

69
00:03:35.500 --> 00:03:38.200
For example, if you are using Windows dotnet core on the

70
00:03:38.200 --> 00:03:41.700
 Raspberry Pi then the C sharp is a good to go for the

71
00:03:41.700 --> 00:03:44.600
 setup and here you will also get the complete details

72
00:03:44.600 --> 00:03:47.500
 regarding different servers. Actually. I already have a

73
00:03:47.500 --> 00:03:51.000
 plan to use a copper cop extension

74
00:03:50.900 --> 00:03:53.400
 for the Chrome browser. But still

75
00:03:53.400 --> 00:03:57.100
 they didn't updated that extension because

76
00:03:56.100 --> 00:03:59.100
 now Google Chrome has been sporting.

77
00:04:00.100 --> 00:04:03.400
Version 3 and still they have a version 2 but

78
00:04:03.400 --> 00:04:06.400
 I hope the guys will update the extension and

79
00:04:06.400 --> 00:04:09.400
 you guys can check that and if they updated the

80
00:04:09.400 --> 00:04:13.200
 plugin then you guys can use that and it's a very beautiful

81
00:04:12.200 --> 00:04:15.700
 ui-based copper

82
00:04:15.700 --> 00:04:19.000
 cop plugin to interact and

83
00:04:18.800 --> 00:04:21.700
 visualize the data in a different format. So guys,

84
00:04:21.700 --> 00:04:24.100
 this is the last video of the corpse section in the

85
00:04:24.100 --> 00:04:25.300
 next section. We're going to

86
00:04:26.600 --> 00:04:29.900
Compare different communication Technologies as

87
00:04:29.900 --> 00:04:33.200
 well as communication protocols. So this

88
00:04:32.200 --> 00:04:35.400
 is the final section from that because next section

89
00:04:35.400 --> 00:04:38.300
 is just conclusion section. So guys see you in the next section. Have

90
00:04:38.300 --> 00:04:39.000
 a good day. Bye.
