►
From YouTube: CNCF Serverless WG 2020-02-06
Description
CNCF Serverless WG 2020-02-06
A
A
B
B
A
A
A
Yes,
it's
funny,
you
go
back
and
look
at
some
of
the
movies.
I
know.
I
know
how
old
you
are,
but
at
least
when
I
go
back
and
look
at
so
the
movies
are
out
when
I
was
a
kid
like
the
original
Bad
News
Bears,
it's
like
oh,
my
gosh
I,
can't
believe
they
actually
showed
that
because
they
could
never
show
half
that
stuff
today,
I'm,
even
even
on
a
movie
exactly.
C
B
Just
gonna
say
one
thing
that
I
find
intriguing
in
the
last
couple
of
weeks
is
I
discovered
this
channel,
where
it
stuff
what
they
call
pre-code
Hollywood
movies,
which
were
from
before
1934
uh-huh,
and
it's
pretty
amazing
what
they
were
showing.
You
know
like
just
the
you
know,
violence
and
beating
up
women,
and
you
know
heavy
drinking
and
it's
like
wow
big,
and
that
was
in
the
30s
by
34.
A
Yeah,
it's
interesting,
I
think
it'd
be
really
fascinating
to
to
take
a
group
of
people
from
back
then
and
drop
them
in
today's
culture
and
take
a
group
here
from
today
and
drop
them
back
in
that
culture
and
just
watch
the
reactions
from
both
sides,
because
it's
funny
you
got
it
yeah,
oh
I,
wasn't
even
that
movie.
It
was
with
I
think
was
with
Sylvester
Stallone
at
that
allowed
to
say
demolition
man
where
he
was
like
a
cop
frozen
in
time
and
then
and
then
yeah.
B
A
B
A
B
D
A
Yeah,
oh
welcome,
if
you,
if
you
type
your
name
and
the
company
you're
with,
if
you
want
to
be
associate
with
a
company
into
the
chats
I'll,
add
you
to
the
to
the
attendee
list.
Just
we
keep
track
of
attendance
that
way
people
can
get
voting
rights
because
we
based
voting
rights
based
upon
attendance.
So
if
you're
planning
on
joining
joining
on
a
regular
basis,
I'd
love
to
add
you
to
the
attendee
list.
Yes,
okay,
quick
and
mr.
Scott,
hello,.
B
A
D
I
A
A
The
reason
I'm
asking
is
because
voting
rights
are
usually
based
upon
attendance
on
the
calls
and
stuff
like
that,
then,
and
if
there's
someone
else
in
your
company
who
may
join
and
may
want
to
say,
okay
either,
one
of
you
can
show
up
to
get
to
get
credit
for
showing
up
today.
But
if
you
think
it's
only
going
to
be
you,
then
that's
fine.
We
can
just
keep
it.
It's
just
you.
If
you
want
yeah.
B
A
All
right,
3
after
why?
Don't
we
go
in
and
get
started?
Let's
see,
Wow
small
group
today
only
70
people
all
right,
let's
see
a
eyes
bleep
are
not,
and
we
thought
about
marking
Kim
but
I
believe
thinking
about
this
every
now
and
then
so
at
some
point,
we'll
have
some
sort
of
some
sort
of
proposal
for
what
to
do
relative
to
us,
going
to
some
sake
or
creating
a
new
one,
all
right
community
time.
For
those
you
knew
the
Karl.
A
So
anybody
have
any
topics
you
want
to
bring
up
all
right,
cool
moving
forward,
then
EU
planning
so
I
believe
relative
to
things
that
we
need
to.
Let
the
the
conference
organizers
know
about
I
think
for
the
most
part
we're
pretty
much
okay,
because
we
have
speakers.
I
know
that
there
were
yes,
the
workflow
guys
are
still
trying
to
figure
out
exactly
who's
talking.
But
if
we
can
worry
about
that
later,
the
one
thing
I
do
want
to
talk
about
today,
if
possible,
is
the
answer
bar
stuff?
This
is
the
booth
thing.
A
A
Thinking
making
half
time
for
each
day
we
get
alternate
morning
or
afternoon,
I
thought
full-time
might
be
a
little
hard
in
terms
of
finding
people
to
actually
staff
it
and
random.
Just
kind
of
bug
me
because
I
don't
feel
like
it's
fair
to
people
who
actually
do
want
to
talk
to
us
to
not
know
for
sure
when
we're
going
to
show
up,
and
it
might
change
but
I
figure.
If
we
can
at
least
say
we're
there,
you
know
morning
or
afternoon,
I
need
to
go
today.
A
D
L
A
M
I
agree
that
random
is
annoying
as
well
Matt
candy.
He
would
be
absolutely
terrible,
not
knowing
when
people
are
there,
so
definitely
not
random.
Full
time
would
be
rather
intense.
So,
like
sounds
good
to
me,
okay,
who
wants
to
man
the
Cal
score,
be
there
right.
We
need
a
list
of
people
first
to
see.
Could
we
do
that?
It
might
be
nice
them
I,
don't
know
if
we're
gonna
get
the
people
yeah.
A
D
A
Okay,
so
I
think
the
real
question,
then,
is
we
just
can't
figure
out
whether
when
what
morning
or
afternoon,
each
of
those
days
and
I
forgot
some
way
to
press
to
sort
of
vote
or
do
something
about
that?
I'll
probably
just
put
together
a
spreadsheet
or
something,
and
you
guys
can
fill
your
names
in
we'll
figure
it
out
done.
O
L
A
A
O
O
Are
you
who's
gonna
bring
the
beer
to
the
booth
I'm
sure
we
could
find
somebody
to
get
you
a
beer
now
I'd
be
fun
to
like
talk
to
people
about
that
during
that
yeah,
it's
good
point,
I,
just
don't
I.
Just
don't
want
to
do.
Thursday
p.m.
because
that's
when
the
swag
run
happens,
people
are
exhausted.
People
don't
want
to
be
there
anymore.
A
A
P
Gonna
say
also
there's
nothing
that
says
you
can't
be
at
the
answer
bar.
Even
if
it's
not
your
specified
time
like
it's
a
it's
a
little
section
and
there's
people
milling
around
all
the
time
and
if,
for
some
reason
they
have
an
empty
booth
and
you
decide
that
you
want
to
be
there,
then
you
can
always
skip
your
name
up
there
and
be
there.
So.
A
P
For
well
for
San
Diego
anyway,
they
they
boo-booed
and
did
not
have
logos,
which
was
problematic.
So
unfortunately,
it
was
just
a
plain
white
fine,
with
the
name
of
the
project
it
still
worked,
but
it
was
a
little
unfortunate
and
so
I
was
told
by
Katie
that
they
were
gonna
fix
that
for
the
next
one.
So
hopefully
it
will
have
logos
and
everything,
but
they
put
them
up
with
like
velcro.
A
A
A
G
A
Me
a
note
with
what
you
want
to
really
say:
use:
messenger,
okay,
fine,
fine,
okay,
anything
else
for
coop
con,
all
right,
SDK
called
we
didn't
have
one
last
week,
so
nothing
to
update
us
on
I
do
believe
we're
on
schedule
to
have
a
call
today,
assuming
people
want
to
talk
so
hang
on
after
the
call,
if
you're
interested
relative
to
the
rest
SDK.
Just
this
morning,
I
did
hear
back
from
these
folks
who
were
students
at
some
University
I,
believe
I,
remember
correctly,
and
they
are
interested
in
contributing
so
I
was
gonna.
A
Try
to
get
a
conversation
going
between
those
folks
and
Francisco
to
see
about
whether
it
makes
sense
to
try
to
merge
these
efforts
and
stuff
like
that.
So
I
don't
want
to
try
to
ask
for
a
vote
yet
because
we
don't
know
exactly
which
project
would
come
forward
or
whether
we
both
kind
of
a
thing
so
I
want
to
have
those
discussions
offline
first
before
we
bring
that
back
to
the
group.
Here.
That's
something
everybody's!
Okay
with
that,
but
also
okay,
Cathy
I,
don't
see
Cathy
on
the
caller
Cathy
you're
gonna
call
Cathy.
A
R
One
thing
that
I
wanted
to
point
out
is
below
the
querying
event
producer
added,
a
new
start
of
a
section
called
registering
with
a
producer
or
an
aggregator
and
I'm
wondering
if
we
should
think
about
a
protocol
to
advertise
that
you
produce
events
that
can
be
discovered
this
little
circular
here.
But
thinking
about
a
comment,
a
really
common
use
case
that
that
I
hear
from
the
customers
that
I
talked
to
is
you
know,
they're
writing
systems
that
they
might
receive
an
event
that
is
triggered
by
some
outside
system.
R
Q
That
means
that
the
producer
at
that
point,
when
it
registers,
when
it
basically
announces
I'm,
going
to
go
and
publish
events
to
that
middleware.
It
also
needs
to
go
and
advertise
which
events
are
going
to
be
published.
And
then,
if
you
have
this
multi
a
multi
level
distribution,
where
you
have
let's
say
a
scenario,
will
you
have
an
a
producer
which
is
a
device
which
publishes
to
an
intermediary
which
is
an
IOT
gateway
that
sits
somewhere
behind
a
firewall?
Q
That,
then,
in
turn
goes
and
publishers
out
into
a
clouds,
IOT
system
called
IOT
infrastructure,
then
effectively.
Anything
that
can
be
raised
by
that
IOT
gateway
must
then
be
further
down
published
into
the
cloud
gateway
so
that,
if
there's
a
downstream
consumer
that
sits
at
the
cockpit,
we
can
know
what's
available
from
the
devices
that
are
upstream
so
there's
some
propagation
of
advertising
data
that
needs
to
happen
in
some
way.
R
Q
And
the
question
is:
how
does
that
happen?
How
do
first,
how
do
we
propagate
the
subscription
and
that's
one
thing-
that's
kind
of
in
the
subscription
API
part,
and
you
know
how
do
we
make
this
so
that
we
can
go
properly,
but
then
also?
How
does
that
consumer
even
know
that
the
green
thing
that
sits
outside
of
that
box
in
one
of
those
other
domains
can
can
raise
that
event?
So
there
has
to
be
some
advertising
propagation
what's
happening.
A
C
Because
that
so
I
agree
with
what
Clemens
is
saying
and
I
think
that
does
all
have
to
happen
internally
but
I
wonder
you
know
if
you
take
a
client
centric
view
to
this
capability.
All
of
that
should
be
hidden
from
them
yeah
so,
for
instance,
yeah.
If
if
we
were
emitting
our
current
webhook
event
stream
using
cloud
events
and
obviously
today,
you
know
what
it
is,
so
you
would
actively
subscribe
to
it.
But
you
don't
need
to
know
all
the
component
domains
within
PayPal
that
actually
are
producing
those
events.
K
Yeah
I
was
just
going
to
add
in
addition
to-
and
forgive
me
if
this
was
this
was
stated
and
I
missed
it
in
addition
to
the
events
being
sort
of
I,
guess,
centrally
or
or
consumable
by
some
through
some
middleware
that
isn't
the
actual
producer
of
the
event.
I
think
we
are
interested
in
in
having
the
same
sort
of
model
for
discovery
as
well.
We
want
we
have
a
Coolio.
We
have
all
of
these
different
systems.
All
these
different
products
at
all
are
going
to
be.
C
C
Say
I
mean
I
wasn't
saying
that
that
function
doesn't
need
to
exist,
I'm
just
wondering
what
it
needs
to
exist
in
the
spec.
You
know
thatthat
sort
of
internal
aggregate,
publish
republish,
you
know
delegated
subscriptions
or
that
sort
little
thing
it's
more
of
an
internal
concern
unless
I'm
not
understanding
their
comment
correctly.
A
You
want
that
new
service
to
be
able
to
register
itself
automatically,
and
so
having
standardized
api's
and
mechanisms
to
make
that
happen
just
makes
everybody's
life
easier.
My
only
concerning,
and
certainly
too
strong
of
a
word
is
whether
that
would
be
part
of
this
piece
of
work
or
a
secondary
piece
of
work,
because
I
think
as
Jim
is
saying,
it
feels
a
little
bit
like
you're
talking
about
a
different,
a
different
role
or
user
would
use
these
api's
right
because
the
subscription
and
the
discovery
stuff.
A
N
S
A
A
R
So
it
as
a
next
action
item
I
was
gonna.
Try
to
put
together
some
example.
Api
calls
an
additional
we
have
there,
which
is
it
helps
me
think
anybody
would
like
to
help
with
that.
That
would
be
awesome.
Are
you
guys
having
very
low
phone
calls
we're
not
if
you,
if
you
would
advise
that
we
should
I'm
happy
to
schedule
that
as
well?
It's.
A
Up
to
you
guys
every
you
know
as
long
as
the
work
gets
done,
I
don't
know,
I,
don't
care
how
it
gets
done.
I
was
just
wondering
whether
you
guys
are
having
an
offline
discussions
on
the
four
of
you,
two
to
figure
out
what
goes
in
the
dock,
good
to
you,
guys
how
you
want
to
work
I,
just
just
curious.
Q
Q
Q
Q
We
have
not
gone
so
far
to
bind
that
to
a
protocol
and
the,
but
we
have
worked
on
the
I
have
worked
on
and
we
all
have
worked
on
the
information
model
because
the
sink
URI
which
I
took
from
your
description
dock
and
where
I
think
we
still
want
to
go
and
change
that
name
to
target
or
something
else,
because
that
is
not
sufficient
for
the
UI
itself
of
the
scheme
of
the
UI
itself.
It's
not
sufficient.
It
became
work.
Q
Protocol
you're
speaking
specifically
there's
stuff
like
like
WebSocket
bindings
for
protocols
which
make
the
UI
WSS.
And
then
you
can't
tell
what
that's
you
know:
mqt
or
whether
that's
Inca
P,
because
effectively
you
learn.
The
client
will
learn
about
this.
As
the
as
the
the
sub
protocol
is
offered,
we
need
to
have
a
special
indicator
for
what
the
protocol
is
supposed
to
be,
and
so
we
have
a
protocol
indicator
MVP
and
then
n
B,
2,
D,
3
and
B
5,
HTTP
and
picofarad
Nats,
I've,
separated,
mp3
and
md5
out
here.
Q
Keep
this
then
for
all
the
protocols
for
the
particular
protocols
there
will
be
protocol
related
settings.
There
is
we're
gonna
scroll
down
in
a
moment,
and
so
those
will
effectively
indicate
all
the
things
that
are
relative,
that
are
specific
to
the
chosen
protocol
and
that
end
point
and
then
the
sink
might
be
the
end
point
and
then
the
conflict.
The
conflict
map
that
was
there
already
will
might
then
hold
information
that
is
not
protocol
specific
but
related
to
that
subscription.
Q
You
could
think
of
as
a
retry
count
or
retry
proration.
We
haven't
really
thought
of
you
know
through
what
that
might
mean,
but
that
is
an
interesting
thing
to
keep
there,
whether
we're
going
to
go
and
take
the
protocol
settings
and
the
config
and
fold
them
on
top
of
each
other
or
something
we're
going
to
go
and
see.
Q
And
then
we
all
know
that
there
we
need
to
have
filters,
and
we
have
decided
that
we
will
one
that
we
will
write
a
section
about
the
filters
that
will
initially
just
cover
some
very
simple
ones,
related
to
the
existing
condiments
properties
or
likely
covering
subject,
source
and
type
with
the
prefix
suffix
and
a
direct
match
filter
as
a
as
a
start
that
we
can
still
think
of.
What
do
we
need
to
have
something?
That's
a
little
more
sophisticated.
Q
If
you
scroll
down
one
and
then
for
the
protocol
settings
there
are
I
filled
out
two
sections
of
the
ones
that
we
need,
which
should
illustrate
what
I
mean
with
protocol
settings.
So
Franchitti
you
might
have
an
endpoint
euro
in
which
simply
points
to
the
broker
and
then
in
the
protocol
settings
you've
defined.
What
the
topic
name
is
that
you
want
to
go
and
send
to
then
you
will
define
whether
you
want
to
have
the
quality
cost
level
of
zero
one
or
two
frying
PGT.
Q
Q
So
this
is
the
placement
that
would
live
in
the
configuration
model
and
then
when
they
want
to
set
a
client
ID
explicitly
what
your
ACT
level
is,
that
you're
expecting
here
and
whether
you
want
to
have
any
retries
and
there's
more
for
other
protocols
and
that
we
can
go
and
set
and
Klaus
has
volunteered
to
start
filling
out
some
of
those
things
until
our
next
meeting
next
week.
So
that's
how
far
we
got
very.
C
No,
this
is
cool,
so
a
couple
of
questions
and
is
commenting
on
this
doc
sort
of
ways
get
questions
in
or
commentary
in,
and
the
other
thing
is
from
a
subscription
perspective,
and
this
is
going
to
go
down
a
bit
of
a
rabbit
hole,
but
you
know
our
customers.
Yes,
they
would
need
both
to
be
able
to
talk
to
our
subscription
endpoint
to
discover
what
they
might
be
able
to
subscribe
to,
but
for
then
asked
to
deliver
stuff
to
them.
We
would
probably
need
both
to
them
as
well.
C
So
the
your
subscription
is
a
bit
of
a
handshake
yeah
where
the
client
is
saying
in
this
instance,
you
get
please
deliver
to
this
endpoint
and
by
the
way,
maybe
here's
some
credentials
that
you
need
to
use
to
establish.
That
connection.
Is
that
there's
sort
of
stuff
that
you
would
be
covering
in
the
that
was
other
sort
of
config
maps?
Yes,.
Q
There
was
a
there
was
an
expensive,
explicit,
credential
field
which
I
cut
for
right
now.
Okay,
because
we
need
to
go,
we
have
to.
We
have
to
figure
out
how
to
do
this
holistically,
because
all
these
there's
there's
a
bunch
of
different
scopes
that
collide
and
for
which
we
have
to
have
an
idea
of
how
to
to
manage
those,
because,
yes,
there's
quite
a
bit
of
the
dance
there's
the
discovery.
Question
of
you
know
who
can
talk
to
the
discovery
service?
Q
The
discovery
service
might
be
living
completely
elsewhere
from
where
the
subscription
endpoint
is
because
the
the
discovery
service
is
kind
of
like
DNS,
and
that
has
publishing
things
over.
There
is
different
from
actually
being
able
to
subscribe.
Then
the
subscription
service
needs
to
have
its
have
a
different
authorization
scope
and
then,
of
course,
when
you
subscribe,
then
you
need
to
go
and
pass
the
the
subscription
manager.
Basically,
some
kind
of
authorization
grant
to
then
talk
to
that
endpoint
and
that
might
be.
Q
C
P
Q
C
Q
K
I
just
wanted
to
add
a
comment
to
the
auth
piece.
There
are
other
ways
of
granting
access
that
don't
wear
off,
might
not
make
sense
in
in
the
negotiation
when
creating
a
subscription
or
sending
events.
So,
for
example,
you
know
a
lot
of
vendors
as
you're
all
familiar
with
have
access
control
mechanisms
that
sort
of
fall
out
of
band
of
all
this,
so
Amazon
Kinesis
right
and
if
I
wanted
to
grant
access
to
that,
I
can
do
that
through.
I
am
and
that's
sort
of
bypasses
the
need
to
do
off
in
mine.
Q
Okay,
so
first
we
have
another
percent
familiar
without
a
double:
yes,
it
does
it,
but
in
but
I
think
they
do
in
a
similar
way,
but
enact
so
in
a
juror.
You
have
these
managed
managed
service
identities
which
are
effectively
the
identity
of
the
process
that
you're
executing.
And
then
you
can
talk
to
one
of
our
managed
services
and
it
looks
like
you:
don't
have
to
go
and
pass
the
credential,
but
all
the
magics
don't
know
the
covers.
Ultimately,
your
clients
still
get
to
get
to
token
and
passes
it's
open.
K
B
Just
wondering
why
he,
the
desire
to
add
to
the
subscription
details
that
have
to
do
with
physical
authentication
and
such
to
the
brokers,
because
so
probably
the
opening
a
can
of
worms
already
mentioned,
was
the
access
controls.
But
you'll
also
need
to
know
things
like
which
broker
can
I
connect
to
which
can't
I
connect
to
where.
B
Multiple
subscribing,
but
because
of
access
controls
between
brokers
for
road
I
mean
I,
assume
the
messaging
layer
will
automatically
do
that
from
the
event
perspective,
all's
I
think
that
would
be
relevant
would
be.
What
is
the
event
so
I
know
how
to
serialize
and
deserialize
over
the
messaging,
and
what
are
the
topics
that
those
events
are
actually
flowing
across?
Q
Of
this
API
is
to
tell
someone
to
deliver
events
to
you.
So
there's
a
there's,
a
there's,
a
there's,
a
foreign
party,
and
you
want
to
tell
that
foreign
party
to
to
deliver
events
to
you
and
you
have
an
endpoint
in
your
system.
That's
the
that's
the
goal
of
the
that's
the
goal
of
this
of
this
API.
So
it's
for
push
style
subscriptions
where
someone
has
events
and
you
want
to
walk
up
to
them
and
subscribe
so
that
they
will
deliver
events
to
you.
Q
That
means
that
you
make
an
endpoint
available
and
that
endpoint
available
may
be
may
not
be
HTTP,
but
one
of
those
other
protocols
and
therefore
you
have
to
go
to
configure
that
relationship.
There
is
no.
There
is
no
out
of
bad
magic
that
you
could
establish.
That
would
make
the
thing
interoperable.
If
you
don't
communicate
all
the
details.
B
But
you
are
again
asking
for
a
client
to
a
consumer
to
producer
direct
relationship
which
is
completely
against
eventing,
with
event
brokers,
where
they
are
completely
decoupled
and
the
producers
and
the
consumers
are
anonymous
to
each
other.
Why
would
you
want
to
suddenly
bind
them
together
in
a
stun
relationship
so.
Q
That's
not
true,
so
if
you,
if
you
go
and
a
new
product
example,
if
you
use
a
very
very
in
every
event
the
producer
produces
into
into
a
topic
and
every
event
written,
it
knows
nothing
but
as
your
event
rate.
But
if
you,
if
you
want
to
subscribe
to
as
your
event
grid,
which
is
a
push
delivery
channel,
then
you
need
to
go
and
provide
to
event
for
it.
You
need
to
provide
an
endpoint,
HTTP
or
one
of
our
built-in
ones,
service,
bars,
etc.
Q
And
then
you
need
to
provide
a
connection
string
or
you
need
to
provide
and
with
which
contains
all
the
information
like
the
credentials
which
contains
the
correct
address
and
the
port
etc.
All
the
information
that
is
required
for
to
know
where
it
needs
to
go
and
connect
to
to
go
and
deliver,
and
that
contains
the
the
protocol,
information
and
everything.
P
Q
Are
describing
is
Doug
if
you
scroll
up
a
little
bit
more,
which
we,
which
we
define
right
here,
so
we
say,
there's
two
fundamentally
different
types
of
subscriptions.
One
is
pull
where
you
walk
up
to
a
intermediary.
If
the
meet
intermediary
is
delivering
events
through
your
channel
and
we're
describing
exactly
how
that
works
in
a
PTT
and
NQ
P&S.
Q
Well,
you
are
effectively
using
the
mechanisms
that
are
in
that
broker,
but
the
what
this,
what
this
particular
method,
in
particular
API,
that
we've
that
were
defining
in
that
on
the
next
page
is
about,
is
how
is
if
the?
If
that
mechanism
is
not
available
in
the
broker,
when
there
is
no
message
broker
that
allows
you
for
pull
or
pulling
events
out,
then
there
needs
to
be
pushed
in
livery
and
push
delivery
necessarily
requires
the
subscription
manager
to
connect
out
and
for
connecting
out
it
needs
all
that
information.
Q
B
B
Q
Perspective
of
the
application
programmer
generally
and
from
their
perspective,
when
they
walk
up
to
a
broker,
they
say
receive
actively
when
they
use
a
pull
model
and-
and
that's
the
that's,
that's
generally,
what
would
pull
is
like
you
receive
something
actively
and
which
they
make.
They
make
something
available
that
acts
that
actively
listens,
and
then
something
shows
up
which
means
stuff
is
being
pushed
to
them.
Yeah.
B
A
B
Again,
my
only
suggestion
is
to
use
term
other
than
pull
and
push
because
they're
overloaded
terms,
they're,
not
really
computer
science
terms,
so
I
think
it's
the
term
where
I
agree
with
what
Clemens
has
for
definitions.
I
just
don't
agree
that
push
and
pull
are
common
enough
that
I'm
using
I
have
the
exact
reverse.
What
he's
saying
is
true,
but
I
reverse
what
I
call
a
pull
in
a
push
when
I
do
a
venting
from
a
bad
brokers.
Okay,.
Q
Synchronous
is
really
you
if
you
are,
if
you're
initiating
an
operation
and
you
get
an
immediate
result,
you're
basically
waiting
for
a
result
and
asynchronous
is
if
you're
initiating
the
operation
do
something
else
and
then
later
be
the
result
either
comes
to
you
or
you
go
pick
pick
the
result
up,
which
means
you
can
do
an
asynchronous
completion
either
using
pull
or
using
push
those
things
compose.
It's
not
it's
not.
Those
are
different
things
well,.
B
Q
So
impulsive
and
full
subscription
is
also
when
you
go,
walk
up
to
the
a
PTT
broker
and
you
say
subscribe.
This
is
that
you,
you
tell
that
you
program
to
send
you
a
message
whenever
a
message
shows
up-
and
this
might
be
a
thousand
messages
that
are
coming
to
you
and
you've,
but
that's
still
a
pull,
because
you
have
opened
up
a
connection
to
that
broker
and
then
the
broker
is
now
surfing
on
that
pipe
is
serving
you
messages,
which
means
you
know.
B
Q
Difference
between
that
activity
and
you
telling
your
telling
a
subscription
manager
to
go
and
open
up
an
MDT
connection
right
and
then
using
the
pop-up
or
the
publish
operation
against
that
endpoint,
because
that
is
the
push
pushing
means.
Pushing
means
in
this
definition
is
that
the
subscription
manager
actively
goes
and
opens
up
a
connection
and
start
sending
events.
So
this
is
the
difference
in
the.
A
P
A
B
A
C
So
actually
I
was
gonna
disagree
with
with
Hines
until
I
actually
read
stuff
that
we're
looking
at
at
the
moment
and
I.
Think
when
I
hear
the
word
words
push
and
pull
from
again
I'll
put
myself
in
the
shoes
of
a
client
yeah.
For
me
a
pull-
and
this
is
a
use
case
we
have
today-
is
where
a
client
comes
to
us
and
says:
can
you
give
me
all
the
events
that
are
due
to
be
sent
to
me?
So
it's
literally
then,
coming
and
saying
give
me
a
block
of
events.
C
You
know
so
that's
then
coming
and
pulling
the
information
from
our
us,
whereas
a
push
model
is
where
a
client
says.
You
know,
please
push
events
to
me
on
this
endpoint
yeah,
and
so
that
so
the
terminology
is
slightly
different,
because
in
a
pull
model
the
subscription
manager
doesn't
deliver
any
events.
All
it
does
is
buffer
the
muck
until
somebody
comes
and
pulls
them,
so
the
I
was
thickness
in
the
notes,
but
that
was
that
was
sort
of
my
term.
Oh
gee,
okay,.
A
Thank
you
Jim,
so
any
30-second
other
topics
or
questions
for
Clemens
about
the
tech
city
I
went
over
okay
cool
in
that
case
I'd
like
to
see,
if
maybe
we
can
close
out
some
of
the
PRS
that
are
open.
So
let's
go
the
first
one.
Here
is
your
service
memory.
This
is
the
cloud
event
spec
the
original
issue.
No
mr.
A
fresh
everybody's
memory,
the
person
who
opened
this
one
up
was
complaining
or
questioning
about
some
of
the
limits
we
had
in
the
spec,
like
the
64k
thing,
whether
that
was
a
hard
limit
or
just
a
recommendation.
So
what
I
ended
up
doing
was
adding
some
text
in
here
and
I
believe
he
gave
a
thumbs
up
to
him.
So
he
was
okay
with
it.
A
A
A
Some
pseudo
experts
on
the
call
have
you
guys,
had
a
chance
to
take
a
look
at
this
one
yeah
like
Scott.
Could
you
take
a
look
at
this
one,
I'd
love
to
get
your
opinion.
I
know
you've
touched
on
stuff
close
to
space.
I
have
no
do
you
want
time
to
look
at
this
or
yeah
sure?
Can
you
can
ping
me
in
the
issue?
Yeah
yeah.
O
A
Okay
will
do
I
feel
bad.
It's
been
waited
so
long,
but
I
don't
want
to
rush
this
one
cuz
I
don't
want
to
screw
people
up
if
they
have
a
tooling.
That's
uses
this
stuff,
so,
okay,
all
right,
administrative
stuff,
this
one's
fun.
So
a
last
week,
all
I
mentioned
potentially
changing
the
government
stock
to
talk
about
how
you
can
be
added
or
removed
from
the
list
of
admins,
with
a
greater
than
50
percent
votes.
A
That's
basically
what
this
says
right
here,
so
you
can
be
added
or
removed,
is
open
a
PR
to
either
add
yourself
remove
yourself.
The
normal
routing
rules
that
we
have
in
general
are
greater
than
50
percent
anyway.
So
didn't
need
to
say
anything
special
there.
The
only
tricky
part
is
well.
What,
if
someone
wants
to
get?
You
know
wants
to
leave
that
group
on
their
own
that
get
voted
out.
You
know,
pull
it
off
the
island
kind
of
a
thing.
Basically,
the
same
thing
you
can
as
long
as
you're,
not
the
last
one.
A
You
gets
open
a
PR
and
you
can
do
a
self
merge
because
we
can't
force
you
to
stay.
However,
if
you
are
the
last
one
there
and
then
talk
about
how
really
we
need
to
have
a
discussion
first,
because
we
have
to
have
at
least
one
admin
to
keep
the
group
alive,
and
so
at
that
point
we
need
to
question
whether
the
group
should
stay
alive
at
all.
A
A
How
do
you
present
yep,
okay,
cool?
Thank
you,
Manuel
I
also
objected.
Think.
Yes,
let's
see
actually
Klaus,
we
have
a
four
minutes
left.
Do
you
want
to
talk
to
your
PR
that
you
just
opened?
You
know
we
can't
approve
it
cuz,
it's
too
soon.
Do
you
want
to
talk
to
us
here
they
open.
Where
was
it
here?
We
go
well.
N
Not
this
cloud
events
plus
Jason
or
whatever
format
is
used
for
the
NA
event
can
be
used
and
then
I
added
the
example
we
had
also
in
the
github
issue:
okay,
yeah
good,
try,
it's
just
I
mean
I'm,
not
a
native
speaker,
I'm,
happy
to
correct
by
boarding.
Whenever
someone
has
some
things.
I
should
correct.
C
N
N
N
C
O
A
A
A
Okay,
you
can
come
off
mute
'litham.
You
know
anybody
else,
I
missed
for
roll
call.
Oh
there,
you
know
he's
there,
okay,
yeah
Hamza.
If
you
can
give
me
your
full
name
and
the
company
you're
with,
and
it's
Chad
I'd
appreciate
that
just
for
the
attendee
list,
otherwise
I
think
everybody
else
is
free
to
go
unless
anybody
wants
to
stick
around
for
the
SDK
call
immediately
after
this
one.
So
I'll
give
you
very
good
people
a
minute
or
so
to
hang
up
in
the
will
start.
The
SDK
call
thanks
already
all
right.
Thank
you.
J
O
O
O
O
For
people
to
consume
it
or
some
other
reason,
I
think
that
the
the
target
audience
for
most
people
would
be
leverage
some
like
some
of
the
convenience
methods
that
help
you
take
the
conical
form
of
a
event
and
turn
it
in
to
something
that's
for
a
transport
or
a
protocol
and
not
take
the
client
wholesale.
So
at
the
moment
that
the
cloud
events
SDK
is
structured
so
that
those
two
things
are
decoupled,
but
there's
more
choices
that
the
client
makes
that
aren't
really
in
alignment
with
what
cloud
event
says.
T
O
Where
you
take
a
conical
form,
you
turn
it
into
the
the
version
four
of
protocol
and
there's
optimizations.
We
can
make
that
we
never
pop
it
out
into
the
conical
event
sort
of
like
how
when
you
in
go,
if
you're
interacting
with
a
HTTP
you
get
there,
you
get
requests
and
responses
and
is
your
job
to
like
decide
if
you
want
to
take
the
buffer
from
the
incoming
request
and
do
something
with
it
not
really
giving
that
choice.
In
my
client
I.
O
F
O
Q
So
I
have
so
what
I've
done?
What
I've
done
from
the
start
is
I.
Have
this
core
thing,
which
is
just
the
college
events?
We
have
have
this
cloud
of
an
attributes
class,
which
is
the
the
thing
you
can't
really
see,
but
that
deals
with
all
the
version
management
and
and
all
this
what
we
need.
It's
well
we're
still
working
on
it.
No,
we
have
a
little
bit
like
seep,
not
much,
but
that
class
deals
with
effectively
the
the
data
model
handling
and
then
there's
the
cloud
event
per
se.
Q
That's
the
thing
that
I
come
for
effectively
because
they
map,
since
I,
don't
have
like
pure
in
could
be
a
pure
Inca
P
surface
I
can
I
need
to
go
and
map
to
the
product
SDKs.
So
literally,
just
pull
that
and
literally
just
pull
that
that
package
for
the
cloud
events
class
and
then
do
all
my
mappings
to
the
transports
then
effectively
separately
into
the
product
SDKs
and
the
the
condiments
SDK
per
se.
Has
you
know
common
methods
to
the
most
popular
SDKs
in
Midland?
Q
But
these
these
product
bindings,
the
transport
bindings,
is
something
I'm
gonna,
add
effectively
in
further
external
libraries,
which
then
use
and
that's
specific
to
c-sharp
use
the
extension
mechanism
where
I
can
effectively
just
add
a
I
can
add
a
to
cloud
event
to
you
know
the
transport
message
class,
but
I
kind
of
have
this
have
this
core
that
this
core
class,
which
is
really
the
cloud
of
an
SDK
which
and
then
we're
using
in
in
the
further
external
libraries
they
do.
The
transport
bindings
yeah.
Q
O
O
Q
Q
So,
that's
that's
something
that
theoretically,
because
of
the
status
of
key
native,
should
really
live
somewhere
else,
and
then
that
yields
a
native
that
a
bit
of
a
split
in
here's
a
you,
use
a
universally
useful
thing
of
how
you
express
and
handle
the
cloud
event
in
in
an
NGO
and
then
here's
another
set
of
classes.
That
then
deal
with
doing
integrations
of
Canadian.
O
And
those
have
been
mentioned,
we
we
have
that
that's
all
over
the
place
right,
there's
nothing.
That's
que
native
specific
and
the
golang
SDK.
The
the
only
thing
that
is
leaky
is
some
of
the
runtime
object
model
that
can
ativ
supports
is
enabled
by
the
cloud
events
SDK.
You
can
do
other
like
wait,
other
a
lot
of
other
things
too,
but
you
know
this:
SDK
is
the
thing
that
drives
a
lot
of
eventing
pieces
inside
the
okay
needed.
Q
L
O
O
O
At
the
moment,
I
always
go
to
the
conical
form
and
there's
been
work
that
allows
buffering
and
like
buffer
copies
between
two
in
coatings
so
like
it
can
read
straight
from
HTTP
buffer
in
and
send
it
to
the
Nats
out.
So
you
avoid
the
intermediate
version
of
that
object.
Oh,
which
gives
like
a
10x
improvement
a
lot
of
the
times
if
the
message
gets,
if
there
isn't
any
other
thing
to
do
with
the
message,
I'm
aware
of
scenarios
that.
O
G
O
A
A
What
I've
been
doing
recently
was
opening
a
pull
request
in
each
repo
to
identify
the
leader
for
that
repo.
So
someone
knows
who
to
go
poke
if
they
have
any
questions.
Yep
I
I
was
gonna
put
this
list
into
the
main
readme
of
the
connivance
repo
at
some
point,
I
just
hope
you
wouldn't
have
to
go
to
each
individual
directly,
yeah
sure
here.
A
Okay,
yeah:
well,
the
one
thing
I
can't
remember:
we
didn't.
Did
we
talk
about
the
Ruby
SDK
I'm
see
a
call
I,
don't
think
we
did.
No,
no,
we
didn't
yeah
I
I
was
gonna
propose,
oh
no,
we
did.
We
did
and
Mark
suggested
that,
rather
than
archiving
it,
we
just
change
the
title
to
say
no
one's
working
on
it.
They'd
renter
has
a
volunteer
and
I
did
that
already:
oh
yeah
yeah
okay,
so
we
did
yeah,
so
I
think
the
only
action
I
am
left
for
me
is
to
actually
put
this
someplace
global.
A
O
Q
The
reason
why
I
asked
that
question
it
was
that
apparently,
as
I
just
learned
over
I
am
from
elsewhere
is
that
the
confluent
is
triggered
enough
by
the
existence
of
the
Java
SDK
and
the
Kafka
binding
that
they
have
look,
take
a
look,
taking
a
look
at
it
and
they're
very
unhappy
with
it,
and
so
apparently
they're
gonna
bring
a
PR
to
the
caca
part
of
the
SDK
in
order
that
be
cool.
Yes,
you
know.