►
From YouTube: Aries-vcx Meeting
Description
Aries-vcx Meeting
C
C
C
C
C
C
C
A
A
A
A
A
D
A
C
E
C
C
E
E
E
E
D
E
C
E
E
E
E
E
E
E
E
E
E
E
E
E
C
E
E
E
E
E
D
E
E
E
E
E
E
C
C
A
A
E
A
E
E
A
A
A
E
Naian:
thing
in
the
code
that
says
that.
oh,:
if
this
this
id
is
being
used,
twice,
then
don't
allow
them
to
register,.
So
that's
not
there,,
but
by
default..
Whenever
you
ask
for
a
new
registration.
it
it
runs
the
ob
like
using
it
is
vc.
x.
it
tries
to
create
a
new
invitation,
each
time,,
but
the
service
is
the
same.
E
E
A
A
D
A
C
A
A
C
C
C
C
C
C
C
C
B
Bogdan
mircea:
on.
bogdan
mircea:,
maybe
let's
go
with
the
first
step..
It
doesn't
necessarily
mean
that
things
have
to
remain
in
the
state
that
they
are.
there
are..
There
were
some
decisions
that
I
kinda
have
to
had
to
make,
for
instance,,
and
I
try
to
describe
them
in
the
in
the
description.
There.
but,.
B
Bogdan
mircea:,
I
don't
know
things
like
having
consistency
among
builders
and
among
messages,
and
like,.
Even
if
you
have
some
protocol
specific
content
that
really
just
has
one
field
and
having
a
builder
for
it,
which
is
not
optional,
and
having
a
builder,
for
it
seems
like
an
overkill.
on
the
other
hand,.
It
will
be
consistent
with
all
the
other
messages.
and.
B
D
B
B
B
B
B
B
Bogdan
mircea:,
but
there's
nothing
in
it.,
so
bogdan
mircea:,
these
kind
of
structures
are
really
there.,
so
you
don't
even
have
to
build
that.
for
instance,.
When
you
wanna
build
a
handshake.,
we
use
message:
entirely.
you
just
pass
in
the
id
and
the
decorators,
and
you're
allowed
to
build
that,
because
the
the
protocol
specific
content
implements
default.,
so
it
yeah,,
basically
just
short
circuited.
Some
of
the
message.
Parts,.
B
B
B
Bogdan
mircea:,
what
I
like
to
call
builder
gymnastics
and
vast
builders,
around,
while,,
you
know,
building
messages
and
just
dynamically
building
them
in
some
some
way..
If
the
process
is
very
convoluted
with
the
builder
implementing
type
state.,
that
means
each
state
is
basically
different,
types.,
so
passing
them
around,.
It's
just
a
normal.
B
B
B
C
B
B
B
B
B
B
Bogdan
mircea:,
maybe
not
all
like,
not
provide
all
the
functionality
that
the
right
builder
provides,,
but
the
functionality
that
it
does
provide
to
be
to
kind
of
use.
The
same.
you
know,
macro,,
attributes
and
and
stuff
like
that
that
the
rive
builder
is
using
to
basically
allow
you
to
just
change
the
derive
macro.
and.
B
F
F
F
C
B
B
B
C
C
F
C
C
F
F
F
F
F
F
F
F
C
C
C
C
C
C
C
C
A
A
C
C
C
B
B
Bogdan
mircea:,
it
it's
kind
of
postponing,.
You
know,
shoving
this
under
the
rug
rather
than
addressing
the
the
real
problem,
I
agree.,
but
you
know,
like.,
and
so
we
are
heading
there.
mira,
just
removed
the
dependency
from
all
the
tests..
It's
just
matter
of
doing
the
work,
and
that
might
take
some
more
time.
Drives..
There
is
like
higher
priority
tasks
in
the
meantime.,
so.
C
C
A
C
C
C
C
C
C
C
C
Patrik:,
so
george
mulhearn:,
this
is
gonna,
be
still
valuable..
I
mean,.
This
is
importance
to
forward
to.
C
B
B
Bogdan
mircea:,
like
it.,
it's
kind
of
preventing
some
stuff
we're
hindering
some
things
here
and
there,
for
instance,.
In
the
the
message
builders.
thing..
I
forgot,
if
using
a
thread
id
somewhere,,
which
is
just
an
argument
to
the
function.,
but
you
don't
even
notice
an
additional
link
anymore.
next
to
the
other
100.
on
the
other
hand,,
I'm
an
idiot.,
I
missed
it.
on
the
other
hand,.
It
would
have
really
helped
to
kinda.
Have.
B
B
B
C
Patrik:
also,
I
don't
know
what
I
was
working
on,
but
made
some
stupid
mistake,
and
if
the
links
were
not,,
there
wasn't
so
many
of
them.
I'll.
Definitely
it
it
th
the
actual
in
warning,,
with
a
mistake
on
rep
or
what
didn't
didn't
await
for
something
that
would
be
actually,.
It
was
confusing..
What's
going
on,
you
know.,
and
the.
C
Patrik:
some.
you..
I
know
some
conflicts,
because
there's
like
we're
going
here
and
there
on
the
test,,
some
refactoring.,
so
maybe,
if
we
do
it
kind
of
create
by
create
that
would
be
good.
w.,
would
you
be
willing
to
kind
of?
take??
I
know.
take
this
initiative.
kind
of
make
those
pr
and
fix
it.
Up.
B
Bogdan
mircea:,
I
was
actually
thinking
about
that.,
but
I
wanted
to
see
what
you
guys
think
about
it..
So
like
pretty
much
like
you
said,,
there's
the
option
of
going
create
by
create
or
even,
you
know,,
the
more
granular
level.
pr,
by
pr,.
If
you're
working
on
something
else
and
just
like
you're
working
on.
B
Bogdan
mircea:
whatever.,
just
some
some
protocol,
george,
is
gonna,
be
working
on
like,
okay,,
that's
new
code.,
that's
matter.!
I
know
you're
we're
you're
refactoring,
the
the
presumptive
protocol
right?
so
in
the
state
machine..
So
you
might
be
fixing
stuff
regarding
that
as
you're
working
on
it,
and
whatever
links
you
encounter
not
necessarily
related
to
the
code.
You're
dealing
with.