►
From YouTube: GMT 2018-04-03 API WG
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
A
A
C
A
So,
thank
you.
I'm
gonna
just
move
that
up
here.
So
we
remember
to
check
in
about
that
again
yeah.
That
sounds
good
cool
thanks
for
doing
that.
I'm
gonna
move
this
one
preachy
Chao
up
as
well,
so
I
remembered
I
asked
him
about
and
it
looks
like
I
imagine
you
noticed,
but
it
looks
like
pianos
chimed
in
so
he
might
be
a
useful
resource
as
well
on
GRP,
see
stuff
yeah.
C
C
C
B
C
A
A
C
So
so
give
you
guys
some
context
to
the
reason
I
put.
That
is
because
we
are
trying
to
program
against
time
to
offer
the
API
that
we
have,
and
then
we
find
out
that
right
now
on
if
the
routes
is
not
up
in
the
process,
for
example,
during
agents
start
of
like
initializations
live
process,
there
is
give
you
a
404
not
found,
and
also
some
of
the
the
API
endpoints
operated.
C
A
PN
points
actually
give
four
four
four
seven
seconds
for
some:
the
cases
where
the
resource
actually
cannot
be
found,
and
that
calls
the
issues
because
because
right
now,
if
the
kind
receiver
404,
it
cannot
really
tell
whether
the
resource
is
actually
gone
or
not,
because
we
do
have
another
situation
where
we
return
for
four.
C
So
I
think
like
there's
a
couple
of
suggestions
for
that,
so
either
all
the
API
endpoints
and
when
the
resource
actually
is
not
available.
It's
gone
now
motion.
Maybe
you
can
return
life
or
for
10:04
nine
I,
don't
remember.
What's
the
status
to
go
for
like
resource
gone,
it's
for
ten
hold
him
for
ten.
Yes,
so
either
we
return
for
10.
C
A
C
D
C
Available
right
now
you
should
not
you
should
I
mean
you
should
reach
fine.
Basically,
it's
a
temporary
error
and
before
the
resource
resource,
not
phone
case,
we
actually
return
floor
for
so.
If
we
do
that,
it's
it's!
It's
not
it's
pretty
clear,
because
when
you
win
a
hundred
CFO
for
and
knows
for
a
fact
that
the
resources
are
found
and
it
don't
need
to
reach
one
because
in
the
other
case,
it's
a
file,
three
unavailable.
That's
option.
Number
one
option:
number
two:
is
the
prostitute
returned
for
four
or
now?
C
C
A
C
Yeah
I
mean
it's
tricky
right,
so
the
process
is
a
library,
so
you
can
dynamic
a
route.
So
whenever
you
find
a
route
does
not
exist,
does
not
necessarily
mean
that
it
won't
be
there
in
the
future,
because
for
my
dynamically
adding
browse
to
to
the
process
layer
like
like
return
return,
403
the
problem
is
return.
403
is
it's
it's
you
don't
really.
You
cannot
really
tell
what
it
is
like
a
temporary
from
retry
immediately
or
like
a
period
of
time.
We
don't
really
know
because
it's
just
like
a
library
right.
A
C
Over
there's,
so
we
do
do
this
basic
amount
of
initialization
in
the
main
CPP
file
right
or
like
we
inject
everything
to
the
to
the
main
actor
of
the
of
the
process.
I
think
there's
probably
a
place
where
we
could
like,
in
the
main
that
the
somewhere
to
you
know
flip
the
toggle
to
suggests
Hulett
process
that
it's.
C
I
know
so
the
process
supports
this.
You
know
real
dynamic,
you
know
changing
of
routes,
but
in
reality
we
just
set
up
everything
beforehand
in
most
cases
right,
so
it
will
seem
like
a
restriction
if
there's
not
a
way,
it's
like
for,
like
dependency
injection
you're
like
building
up
the
object
graph
and
there's
like
endpoint
to
that,
you
don't
have
a
way
to
signal
that
back
to
the
process.
So
sounds
like
some
improvements.
C
C
A
C
I
mean
yeah
I
think
that
the
standards
say
that
you
can
retry
and
when
you
receive
for,
for
it
does
not
mean
that
the
resources
actually
gone.
So
in
my
appear
later
so,
but
what
the
clients
lodgings
gonna,
be.
It's
gonna
be
like
what
kind
either
a
need
to
reach.
Why
but
yeah
I
I
think
it's
very
hard
to
figure
out
the
client
logic
when
I
receive
404.
C
Depends
on
what
kind
of
API
you're
exposing
like,
for
example,
if
you
are
doing
a
remove
API
and
if
the
remove
you
your
404
so
right
now,
okay,
so
sir
I
give
you
some
context,
the
department's
a
solid
for
like
a
loop
and
you
remove
that
nasty
container,
API
call
and
if
the
continue
has
been
removed
already.
So
previously,
we
returned
full
of
floor.
C
C
Right,
how
do
you
know
I
want
to
keep
track
of
all
the
things
that
you've
already
removed?
Know
if
you're
not
following
return?
200?
Ok,
you
know
that
you
know
for
a
fact
that
the
container
is
not
there
anymore.
So
the
remove
will
be
ok,
so
you
can't
keep
you
can
keep
issuing
remove
I.
Even
if
you
didn't
got
a
response,
you
can
say
hey.
We
issue
the
remove
and
still
watch
for
200.
Ok,
if
I
receive
it
to
you
on
your
ok,
I
know
that
the
container
has
been
removed.
C
I
can
proceed
with
the
rest
of
the
cleanup
logic
in
my
client,
okay,
the!
When
do
you
return
404,
we
don't
return
404
in
that
case,
so
there's
no
4,
4,
4
or
I
can
remove
like
remove
nasty
container
and
move
does
provide
a
config
things
like
that.
Mm-Hmm
just
make
the
remove
item
potent.
Similarly,
we
made
the
launch
item.
Potent
I
think
it's
nice
to
to
design
those
API
to
be
item
potent.
So
the
client
can
just
call
those
if
it's
enough
to
not,
you
know,
get
response
at
all
off
the
timeout.
C
So
it's
a
good
user.
It's
a
good
design
choice
to
make
on
those
api's
idempotent
in
a
distributed
system.
So
that's
what
you
solve
the
issue,
I
think
that's
kind
of
what
we
do
trying
to
do
for
the
resource.
Config
sorry
was
provide
a
clinic
thing,
but
some
of
the
other
UC
API.
We
cannot
change
because
the
backwards
can
kind
of
better
the
issue.
C
I
don't
know
for
sure
that
if
people
are
relying
on
this,
it's
behavior
but
I
think
we
should
provide
some
guy
on
whenever
someone
proposing
an
opportunity
I
how
to
design
that
if
we
say
that
ok,
the
guy
the
guideline
is
like
when
you
design
your
API
and
make
those
calls
idempotent
and
instead
of
return,
flow
or
flow,
should
be
returned.
300.
Okay,
if
we
know
for
sure
that
the
objects
not
there,
that
will
be
an
acceptable,
acceptable
way
of
doing
that
too.
C
So,
I'm,
just
like
throughout
those
ideas
like
who
we
can
do
food
I
mean
it's
not
about
that.
The
problem
we're
trying
to
solve
right
now
it's
about
like
what
are
the
potential
guidon
I
want
to
provide
once
I.
Might
it
is
idempotency
to
me
means
that
you
can
keep
calling
the
thing
without
side
effects
now,
if
the
first
time
it
returns
200
and
the
next
time
the
returns
404,
but
there's
no
satisfied
sounds
like
still
edible
and
the
client
can
just
recognize
that
it's
two
hundred
four
four
are
both
good
in
that
place.
C
Yeah
I
mean
you
can't
you
can't
argue
that,
like
it's,
yeah
I
mean
yeah
I
mean
I.
Think
like
there
might
be
a
different
slightly
difference
between
like
a
true
idempotency
versus,
like
you
can
call
the
call
multiple
times,
there's
no
side
effect,
but
the
return
code
is
different
like
maybe.
There
is
a
slight
difference
between
use
to
the
area
of
the
item.
Potent
let's
see
I
guess
like
for
given
that
issue
right
now
and
I.
Think.
A
C
I
mean
otherwise
it's
very
hard
to
let
the
kind
know
like
which
what
exactly
happened
when
you
reach
between
receiver
for
for
it,
cannot
can
do
nothing
basically,
either
it
has
to
retry
and
get
a
four
foot
again
and
don't
know
what
to
do
next
or
I.
Think
for
503
is
because
think
about
like
when
a
master
is
created
but
hasn't
been
in
trouble.
C
D
C
The
reason
I
think
yeah
I
agree
like
file
3,
make
that
part
consistent,
but
I
think
that
the
fact
that
live
prostitute
you
return
for
four.
If
the
Rao
is
not
found,
I
say,
as
you
mean,
the
rock
can
be
a
dynamically,
then
we
still
have
a
chance
to
return
for
four.
If
your
API
is
actually
based
on
a
dynamic
morale
step,
we
some
code
added
later
after
initialization
is
done.
So
that
part
is
not
soft.
Yet,
basically
we're
saying
that
we
found
that
problem.
We
don't
think
that's
a
problem.
A
C
A
C
I
think,
like
the
return
Pole
three
solve
the
second
browse
problem,
doesn't
solve
the
time
to
browse
problem.
We
still
have
the
same
issues
if
routes
can
be
added
dynamically
so
well,
it's
just
thing
is
like
memory.
There's
like
I
can
activate
call
to
Allah
process
to
basically
activate
the
end
point
in
a
semantical
sense
that
will
and
before
the
activate
method
is
called
it's
gonna
return.
You
5:03
will
that
work.
C
That's
not
gonna
work,
because
I
think
we
also
search.
For
example,
you
are
adding
a
route
like,
for
example,
/,
po
/
bar
and
before
you
are
adding
the
route
even
before
you
call
it
in
the
front
like
a
route
to
add
this
route,
lacrosse
is
gonna,
give
it
give
you
full
or
unless
we
change
daya
as
well.
Well,.
C
A
C
You
is
saying
is,
if
say,
the
routes
being
added,
but
we,
but
we
are
not
all
ready
yet
like
before
we
calling
this
activity,
we
were
temple
3
on
that
particular
routes.
No,
it's
I
mean
all
around
itself
might
not
be
found
like.
What
are
you
doing
that
case?
No
I
mean
for
everything.
Even
if
the
route
is
there,
it's
still
gonna
returning
503,
because
it's
like
the
your
you're
like
creating
this
semantic
that
the
lacrosse
is
endpoint,
regardless
of
the
routes
and
actors.
C
C
C
C
C
Okay,
stay
that
case.
Did
you
want
410
right,
so
you
just
then
yeah
I
mean
that
I
mean
that's
one
of
the
suggestion
that
give
like
either
we
say
that,
okay,
when
you
design
the
future
ranges,
I
offer
the
API
try
to
use
410
if
you
cannot
find
the
resource
anymore
so
that
we
can
distinguish
from
the
404,
which
might
be
the
case
where
the
row
is
not
found.
C
That's
what
acceptable
answer
sure
we
just
have
to
remember
all
of
the
we
have
to
yummy
I
mean
I,
don't
I
don't
want,
like
some
employ
return
for
for
England
off
phone
case
and
the
infirmary
Chennai
for
Tang
and
off
on
case
I
want
to
have
a
consistent
error
code
across
the
API
from
ASOS
I
understand
the
fact
that
we
may
not
be
able
to
change
somebody's
seeing
api's,
but
moving
forward.
I
thought
all
that
new
offers
API
so
need
to
think
through
it
and
and
recommend
people
to
use
for
TANF.
C
D
D
C
C
But
yeah
I
think
even
diet.
I
mean
implementation,
wise
I
think
it's
not
trivial
like
like,
like.
Are
you
saying
that
we
we
still
use
agent
to
add
those
routes
in
Asian
actor
and
the
after
Asian
actor
finishes
initialization?
We
call
some
koala.
You
know
the
process
they
activate
for
that
it
will
translate
that
into
into
something
that
mark
thirty
process
of
knowledge
and
file.
Three
after
that
point,
yes
got.
A
C
Implementation,
wise
is
not
I
mean
we
think
in
paintings
that
call
sure,
okay
right.
So
now
it's
it's!
It's
like
if
you
want
so
the
agent
actor
calling
that
is
probably
not
appropriate,
but
you
could
do
so.
You
want
me
to
choose
between
things
who
inject
the
agents
versus
you
create
within
the
agent.
Then
you
can
choose.
If
you
want,
you
want
to
make
sure
the
thing
is
initialized
before
the
agent
actor,
then
you
can
initialize
it
and
the
main
method
injected
into
the
aging
right.
C
D
C
D
Actually,
I
have
a
huge
case
that
it's
a
little
bit
related
to
this
dynamic
route,
adding
so
one
new
API
we
introduced
in
one
five
is
dynamically:
adding
or
removing
resource
provider
conflicts,
and
that
is
a
bet.
Api
is
appended
by
a
Cameroonian
internal
chemical
research.
I
provided
demon
logo
result
for
a
demon
initially
when
this
will
design
an
ogre
research
or
a
demon.
D
It
is
like
when
we
started
when
we
create
a
demon,
we
instantiate
all
the
first
provider,
but
then
we
figure
out
that
do
for
the
in
stage
instantiation
of
the
resource
provider.
We
need
the
agent
ID
or
state
ID,
because
agent
ID
can
can
only
be
obtained
after
the
agent
finish
the
registration
or
the
graduation.
D
So
currently,
the
way
we
do
is
I
have
what
I
initialize
the
demon
at
agent
in
ization,
but
whenever
you
receive
any
call
like
the
handler
will
just
fight
with
bad
requests
until
ragin,
Godfried,
ready,
search
and
got
the
ID
I
have
not
a
special
call
to
tell
the
demon
to
sell.
Now
you
can
serve
those
things
normally.
D
So
this
is
like
a
little
bit
related
to
this
dynamic,
dynamic,
adding
wrote,
wrote,
although
I
didn't
do
that
right
now
we
have
this
the
other
work
round,
but
if
we
have
dynamic
the
week,
we
actually
can
make
this
dynamic
if
we
want.
So
this
is
a
use
case
that
we
may
be
able
to
use
this
dynamically
without
adding
people
yeah.
C
C
Now
like,
since,
we
hide
the
routes
in
the
actor,
and
we
only
have
one
data
gauge
so
basically
like
if
you.
C
A
C
A
C
Art
doesn't
yeah
if
the
pearl
doesn't
cover
all
the
cases,
for
example
on
way
to
a
get,
and
you
cannot
find
the
object.
I
will
have
a
get
right
now,
but
I
have
a
tactic.
Let's
assume
that
you
won't
get
some
resources
with
an
identifier
and
somehow
the
API
handler
cannot
find
that
resource
when
you
return.
In
that
case,.
D
D
C
C
A
D
B
A
C
Maybe
it
would
say
that
this
is
case
by
case,
maybe,
and
given
that
we
need
to
do
api,
reviewing
this
forum
and
for
any
new,
if
you
have
anything
adding
tomatoes,
maybe
we
can
keep
that
in
mind
and
whenever
someone
propose
some
new
dapi,
this
is
the
first
checklist
that
needs
to
do
to
make
sure
that
the
client
can
actually
it's
english
between,
like
cases
yeah.
A
C
C
C
C
So
so,
I'm
pretty
sure
4G
RPC
will
gonna
have
the
same
debate
because
jury
has
a
bunch
of
similar
error
code,
similar
to
actually
be
status,
that
people
need
to
map
to
different
situations.
D
Fourth
option:
nuts
may
seem
a
little
hacky
right
now.
If
could
it
be
that
the
for
for
returned
by
the
process
is
like
empty
forward
for
and
we
probably
require
the
API
when
they
return
forward,
they
need
to
be
have
a
Content
body.
This
sounds
hacky
right
now,
but
I
remember
I,
seen
something
similar
in
the
codebase
I
forgot
wait,
but
that's
very
hard
to
explain
good.
C
C
C
There
yeah
I
guess
it
will
be
less
in
the
issue
for
JRPG,
because
your
PC
has
this
logic
error
codes.
Also,
we
have
the
error
details
that
we
can
cut
some
structural
information
there,
so
it
probably
less-
and
the
issue
in
geography
see
world
where
we
can
actually
put
some
structure
information
to
find
the
type
of
data
structure,
information.
A
C
So
I
don't
suggest
that
every
new
API,
let's
discuss
that
case,
keep
in
mind
that
there's
in
the
issue
a
regarding
404
and
every
time
people
propose
some
new
API
in
this
forints.
We
need
to
look
into
each
individual
API
and
make
sure
they're
doing
you
can
handle
the
case
and
provide
some
somatic.
A
client
cache
to
use
I
mean
we
can
do
right
now
like,
for
example,
the
world
we
decided
to
do
for
our
resource
provider.
C
C
A
C
A
Nope:
okay,
the
next
item
on
the
agenda.
I
put
this
on
this
task
deadline
proposal
that
had
been
brought
up
on
the
mailing
list.
I
know:
G
tau
was
not
able
to
make
this
meeting
and
I
didn't
reach
out
to
any
I
think
James
P
G
as
shepherding
this,
so
it
might
actually
make
sense
for
me
to
just
bring
this
up
on
the
email
throughout
on
the
mailing
list.
I'm,
not
sure
how
much
context
folks
have
here
around
this
issue,
but
I
think
my
primary
question
just
high
level
question
I
was.
A
A
And
the
other
thing
I
wanted
to
bring
up
just
a
reminder
to
folks
that
I
created
this
ticket
for
tracking
tech
debt
related
to
v2
API,
like
things
that
we
want
to
make
sure
we
address
in
the
v2
API
or
things
that
we
need
to
do
before,
we'll
be
ready
to
transition
and
implement
v2.
So
just
a
reminder
that
this
ticket
exists
makes
those
8700,
if
you
know
of
any
issues
along
those
lines
or
create
any
in
the
future,
you
can
add
them
to
this
epic.
To
track
them
inside
should
practice.
A
C
A
C
D
A
A
B
B
B
A
Nope,
okay!
Well,
thanks
for
joining
today,
everybody
appreciate
the
discussion
I'll
take
on
my
action
items
and
next
meeting
happens
in
two
weeks.
Let
me
know
if
there's
anything
interesting,
you
want
to
add
to
the
agenda
anything
you
want
to
talk
about
and
I'll
send
out
an
email
before
the
next
meeting.
Thanks
for
joining
everybody
have
a
good
one.
Thank.