0:00:57
oops i apologize guys i was having a bit
0:00:59
of a tentacle glitch
0:01:01
but now it's all sorted so yeah welcome
0:01:04
back to another session of buildbreaking
0:01:07
brought to you by the raw coders and
0:01:13
episode we're going to be continuing
0:01:16
from yet today but first of all let's
0:01:19
pay our respects to the elders of the
0:01:21
past present and future
0:01:24
so there we go i begin today by
0:01:27
acknowledging the traditional custodians
0:01:29
of the land on which we gather today and
0:01:32
pay my respects to the elders past
0:01:34
present and future i extend their
0:01:36
respect to aboriginal and torres strait
0:01:39
islander people here today
0:01:42
all right so that was smoothly done
0:01:47
yeah let's choose our background music
0:01:51
so to do which one should we choose this
0:01:54
time let's have a look
0:02:14
remember uh in the previous stream and i
0:02:18
do apologize i wasn't able to make it
0:02:21
yes today because there was a bit of a
0:02:26
last minute thing happened but
0:02:29
now it's all good i am back
0:02:34
and yeah so yes today um
0:02:42
sunday what we did was basically we
0:02:45
uh implemented the
0:02:47
functionality they when we press the
0:02:58
show the user that is loading as in with
0:03:03
and then take us to the next page when
0:03:07
the process is done
0:03:09
all right so um in this one we're gonna
0:03:12
be working on something different so
0:03:17
let me open up my jira
0:03:21
get the ball rolling from there
0:03:37
uh what did i want to do yeah
0:03:45
i'm going to share my screen
0:03:51
and there you go we'll open up jira and
0:03:54
see where we're at
0:04:03
there we go that's the email
0:04:33
what we're gonna do is um
0:04:37
we will convert back the websocket
0:04:40
afterwards uh websocket connection time
0:04:44
needs to be extended
0:04:49
let's actually look into this one
0:04:55
inform user of this connection all right
0:05:00
we can basically implement this first as
0:05:03
in when the websocket is closed we need
0:05:06
to inform the user that you're
0:05:10
you're no longer connected to the
0:05:12
websocket all right
0:05:17
i'll look and that would be done in
0:05:19
basically um in the front end so i'll
0:05:23
open up my terminal
0:05:27
now zoom in a bit you guys can see as
0:05:36
all right and that's
0:05:42
yep and show progress by is done so
0:05:45
because this one is all done
0:05:49
um what we're gonna do is create
0:06:04
connection disconnect yeah
0:06:07
so let's create another branch
0:06:48
so we are over there now and
0:06:55
where's our websocket getting
0:07:15
thing to say disconnect as well
0:07:24
so this would basically be like
0:07:28
anyone there yet no
0:07:34
so what's gonna happen is
0:07:44
all right it's open on message is closed
0:07:59
but before using it
0:08:16
uh what's up download
0:08:40
so left socket url is this
0:08:45
that works okay yeah that's fine
0:08:52
click to prep socket
0:08:54
so is this one websocket error
0:09:00
so it returns a promise
0:09:13
and then it goes in that one board id
0:09:16
it opens up the websocket which is great
0:09:21
and then on connect
0:09:25
and then error okay if there's an error
0:09:33
so we need something
0:09:36
like that but for disconnect
0:10:00
they will return a promise
0:10:06
i'm so capable right there
0:10:56
so let me just connect next
0:11:00
it is a resolve reject error on error
0:11:07
here we want it to resolve
0:11:17
whenever we don't want to show any error
0:11:30
i think this is it really
0:11:33
so if it's disconnected
0:11:37
then what will it do basically we just
0:11:48
resolve to disconnected
0:12:04
all right let's go in our
0:12:15
what does it have to offer
0:12:27
uh my phone is there
0:13:11
okay my api gateway
0:13:30
so what we connect
0:13:32
this is our disconnect isn't it so we
0:13:35
need to connect it to that one lambda
0:13:39
always a lambda on
0:13:42
websocket disk connect handler
0:13:49
it's basically what we need to do is
0:13:55
we need to implement that disconnection
0:13:58
the disconnection as well
0:14:08
thought i already did it
0:14:11
anyway let's go on to
0:14:42
okay oh that's the wrong one
0:14:46
supposed to do it hey
0:15:01
no not in this one
0:15:05
did not match any phone not yet
0:15:08
ah i forgot the um
0:15:18
and now we open this one
0:15:33
okay and disconnect is here
0:15:37
there you go on board is present oh so
0:15:40
it's already implemented two hours max
0:15:44
inflation can be connected ah so we
0:15:47
don't really have to implement
0:15:53
the timeout because
0:15:56
there might be no session more than two
0:16:24
how do we use connect
0:16:33
okay how are we using connector
0:16:36
join your website you click your a board
0:16:38
id that wants to get local so yeah
0:16:49
which comes then here
0:16:53
time to live handler
0:16:56
probably this is the one
0:17:19
already time to live
0:17:24
connected all right
0:17:26
so we're connected and this one would be
0:17:31
no connection id disconnected
0:17:42
yeah so pretty much we have to do this
0:17:53
do it with the lambda disconnect
0:17:57
because that might not oh so it's
0:18:01
so all we need to do is basically just
0:18:06
you don't have a lambda point in the api
0:18:20
okay let's go to cloud formation
0:18:24
because all the stack is there
0:18:33
just connect function
0:18:36
hello world onto the dirt
0:18:43
this connects function road is gonna
0:18:45
permission disconnect
0:18:51
handler function yeah there is the one
0:18:56
so we basically need this one
0:19:24
you use the hammer proxy yet that's fine
0:19:29
there's all right that's all right cool
0:19:33
is that the same as well whoops
0:19:36
there's something not right
0:19:39
this is this has the air in it
0:20:31
what we can do actually is
0:21:01
so can is all there but we just have to
0:21:11
so we would have to do it under
0:21:14
the proper websockets so all this that's
0:21:27
all right um since i don't have anyone
0:21:32
i'm probably gonna call it a day
0:21:38
i can test it with
0:21:43
yeah yeah i need another user to test it
0:21:47
so yeah probably have to wait for
0:21:52
raw coders to come
0:21:55
tomorrow and hopefully we can we can
0:22:17
i wanted to test um the websocket
0:22:20
disconnection but since um it won't work
0:22:22
if i'm under the same network
0:22:25
i need one of the other rule coders to
0:22:28
come online and help me out which will
0:22:30
probably be done tomorrow
0:22:35
i i didn't actually think that
0:22:40
websocket function that he has
0:22:43
isn't even is even implemented but but
0:22:46
he is so thanks a lot for tori for
0:22:49
doing that i'm pretty sure he was the
0:22:52
that is our node.js front-end expert
0:22:57
so yeah we will carry on tomorrow
0:23:02
same place and the same task and if you
0:23:05
want to check how we test it out feel
0:23:09
all right until then take care of
0:23:12
yourselves and i'll see you tomorrow
