►
From YouTube: 2022-04-19 meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
C
B
But
they
were
doing
a
lot
of
double
shot
stuff
at
microsoft,
while
I
was
there
for
their
zune
and
then
for
some
some
xbox
accessories
as
well.
C
C
B
Yeah,
this
is
mostly
like
stuff
for
the
living
room
and
things,
but
yeah
cool
company.
C
B
A
All
right,
let's
start
so
I
have
a
couple
items
there.
So
the
first
one
is,
I
implemented
the
the
new
transport
that
playing
http
transport
for
all
pump
in
go
the
pr
is
there
and
they
reviewed
it.
Thank
you
andy.
It
would
be
great
if
I
could
get
one
more
review.
Checkmark.
If
you
have
time
it
would.
D
D
A
A
So
once
we
have
these
two
things,
probably
I'm
going
to
look
into
having
this
as
a
feature
of
detailing
of
the
open
cloud
tree
as
the
case,
the
the
ability
to
receive
the
configuration
remotely
anyway,
we'll
see
we'll
see
where
that
goes.
So
that
was
the
first
one
and
the
second
one
is
we
discussed
this.
I
think
a
couple
meetings
back
and
there
was
a
pr
yeah
david.
A
You
proceeded,
so
we
made
this
change
where,
whenever
the
connection
is
dropped
and
that
the
client
reconnects
the
agent
reconnects
with
this
new
change
now
it
sends
the
status
report
immediately
upon
reconnection,
which
is
correct,
which
is
what
the
specification
requires.
However,
there's
a
nuance
which
I
missed.
But
if
you
read
the
specification
it
says
that
if
the
description
of
the
agent
didn't
change,
then
it
should
not
be
included
in
the
in
the
status
report.
A
C
Yeah,
I
guess
my
my
impression
is
that
you
wouldn't
have
that
information
unless,
unless
you
had
stored
it,
which
you
could
store
it
by
the
agent
id,
but
it
could
have
disconnected
for
you
know,
hours
or
days
or
weeks
and
when
it
reconnects
you,
you
don't
have
the
other
information
about
the
agent
and
I
don't
know,
is
there
a
way
to?
I
know
you
can
request
the
effective
configuration.
Can
you
request
this
description.
A
You
cannot
request
the
the
description,
but
if
that's
what
we
need,
that's
essentially
the
the
exact
same
situation
right
when
you
lost
the
effective
configuration
for
whatever
reason,
maybe
your
server
restarted
right,
store
or
whatever.
I
think
this
is
similar
right.
You
lost
the
description,
so
maybe
the
server
can
ask
in
exactly
the
same
way.
It
can
be
just
another
flag
in
the
or
whatever
it's
called
request
plugs
or
whatever
we
call
it.
A
So
if
it's
necessary,
I
think
we
should
do
that
instead
of
including
it
every
time
I
mean
it's
a
small
amount
of
data.
Technically
we
could
include
it
like
the
configuration
could
be
large.
That's
why
I
guess
it
was
one
of
the
reasons
why
I
didn't
want
it
to
be
there
every
time.
The
description
is
a
bunch
of
attributes.
It
can
be
very
large,
like
I
am
probably
maybe,
instead
of
over
complicating
it,
making
it
another
round
trip
for
the
server
to
tell
I
don't
have
it,
please
send
it.
A
Okay,
but
then
what
do
we
do
with
with
http,
because
with
http
there
is
no
persistent
connection,
all
the
all
the
status
reports
are
in
any
way
from
the
previous
ones
right.
So
what
do
we
do
there?
Do
we,
if
we
don't
require
it
to
be
included
every
time
we
have
the
same
problem
for
for
plain
hdp
transport
right.
A
C
Saw
that
in
the
spec
of
of
how
that
was,
you
know
defined
as
a
pulling
and
really
ability
for
the
server
to
respond
more
so
than
the
agent
to
identify
itself.
But
but
it
is,
you
know
the
server
could
easily
want
to
respond
with
asking
the
agent
to
identify
itself
so
yeah
yeah.
So
I
think
I
think
I
think
it's
both
I
I
I
would.
I
would
prefer
to
save
the
round
trip
when
I
think
you're
always
going
to
want
the
agent
information
when
it
connects
yeah.
A
C
Implementation,
even
even
the
effective
configuration
we
ask
for
that,
the
first
immediately
on
connection,
because
I
just
don't
trust
that
I
have
the
most
recent
information,
even
if
yeah,
even
if
it
should
have
told
me
if
something
changed,
you
know
if
I
haven't
heard
from
it
for
a
while.
I
can't
trust
what
I
what
I
know
about
it.
C
So
I
would
I
would
probably
just
since
I'm
already
doing
a
round
trip
to
ask
for
the
effective
configuration.
I
would
just
add
that
flag
to
ask
for
the
agent
identification
as
well,
and
I
and
I
think
we
would
be
okay
with
that.
A
E
Well,
as
far
as
sending
the
status
report
I
mean,
is
there
a
way
for,
like
the
you
know,
I
don't
think
the
client
knows
if
it's
the
first
time
it's
connected
or
if
it's
just
reconnecting,
does
that
make
sense
like
it
wouldn't
really
know
when
to
differentiate
like
oh,
this
is
the
first
time
I've
talked
to
the
server
or
it
was
the
connection
lost.
Then
I'm
reconnecting.
E
A
Yeah,
no,
we
should
send
the
status.
I'm
not
saying
we
shouldn't
send
this
out.
It's
just
whether
we
include
the
description
all
the
time
we
do
know
right.
If
it's
a
reconnection,
the
agent
knows
that
this
is
not
the
first
time
it
is
connecting.
So
we
can
make
that
decision
to
include
or
not
include
the
description.
A
That's
that's
the
question
I
have
I'm
I
I
absolutely
agree.
The
status
report
should
be
sent
all
the
time
when
you
connect
the
first
time.
Otherwise
I
mean
you
have
to
send
something.
Otherwise
it's
just
you're
opening
a
connection
and
not
doing
anything.
So
that's
that's
the
first
message
you
send
you
send
a
status
report.
That's
that's
fine.
I
think
nothing
needs
to
be
changed
there
in
the
logic
and
that's
how
the
spec
requires
it
to
be.
It's
only
about
whether
to
include
or
not
include,
the
description.
A
C
A
C
C
A
Yeah
again,
I
agree
with
you
if
we're
talking
about
the
websocket,
but
if
we
talk
about
the
http
there's
no
first,
second
or
anything
right,
it's
just
randomly
appearing
requests
from
somewhere,
so
yeah,
okay
anyway,
I
I
guess
I
need
to
think
a
bit
more
on
this
myself
as
well
I'll
just
open
an
issue
for
people
to
also
post
their
thoughts
there.
I
want
to
understand
what
do
we
do
with
web
socket?
I'm
not
concerned.
We
can
include
it
every
time
the
reconnects
are
going
to
be
very
rare.
So
it's
not
a
problem.
A
A
A
A
Okay,
yeah
I'll
open
an
issue
anyway,
okay,
and
just
give
it
a
big
time.
I
want
to
think
about
it:
okay,
cool!
I
I
only
had
these
two
things,
anything
else,
guys
anything
that
you
have.
You
want
to
talk
about.
F
I
had
a
very
simple
question
actually,
and
we
were
talking
about
agent
description
so
based
on
the
spec
that
usually
refers
to
having
attributes
like
the
service
name
and
the
us
versions
and
the
rest.
So
you
did
point
to
the
fact
that
these
can
be
large
right.
So
does
the
effective
config
as
well
kind
of
come
in
within
this
itself,
the
configuration
or
is
it
just
more
or
less
attributes
that
we're
speaking
about
within
the
space.