►
From YouTube: CNCF Serverless WG 2020-03-05
Description
CNCF Serverless WG 2020-03-05
A
A
A
A
A
A
F
F
F
F
F
F
F
B
A
A
A
A
H
A
I've
had
many
conversations
with
companies
who
tend
to
run
run
owned
being
control
upper.
Do
you
want
to
call
it
particular
open-source
projects
and
they're
all
located
in
one
particular
area
and
I?
Keep
telling
them
have
everybody
work
from
home
for
a
while
and
experience
what
it's
like
to
not
be
in
the
inner
circle
or
be
hanging
around
the
water
cooler
to
be
able
to
have
those
those
chats
and
hear?
What's
going
on?
It's
not
fun
so
I
understand.
G
B
A
G
E
I
K
A
All
right,
everybody's,
nice
and
early
today
it
actually
might
be
a
short
call.
Cuz
short
agenda
couple,
PRS
review.
Actually
well,
you
guys
are
waiting
since
we
usually
don't
start
till
three
after
you
guys
wanna
take
a
look
at
the
in
particularly
the
first
PR
in
the
list.
This
is
sending
encoding
of
Kafka
the
hitters
to
see
what
you
guys
think
in
there,
because
there
was
a
must
that
was
out
of
there.
I,
don't
think
it's
a
big
deal,
because
I
think
that
was
the
intent
all
along.
A
K
A
Can
do
me
a
favor,
and
here
they
paste
a
link
in
the
chat.
Here's
a
link
to
the
meeting
notes
either
put
your
company
name
next
to
your
name
in
the
meeting
notes
or
just
type
into
the
chat
and
I'll.
Add
it
for
you
just
want
to
make
sure
I
get
your
associate
of
the
right
company.
Is
that
something
you
want
to
be
associated
with
a
company?
And
then
Vinay?
Are
you
there?
Yes,
I'm
here,
I
apologize
for
you?
Is
this
your
first
time
in
I
can't.
A
A
A
A
A
Sorry
in
the
zoom
chat-
and
you
just
put
your
full
spelling
of
your
last
name
and
the
company
with
just
so
I-
can
get
it
right
for
the
attendance
yes
cool.
Thank
you
appreciate
that
all
right
and
it's
three
after
so
one
we
go
ahead
and
get
started,
got
a
question
for
you
guys.
So,
a
long
time
ago,
when
we
were
talking
about
a
new
icon
for
cloud
events,
I
believe
Austin
took
an
action
item
to
change
the
tagline
on
the
on
the
sticker
and
then
the
icon,
I,
honestly
Carol.
A
Why
people
didn't
like
it,
but
I
figure.
It's
been
know
long
enough.
No
one's
complain
about
it.
Does
anybody
have
any
problem
with
just
closing
out
the
say,
I
can't
imagine
it
really
matters
that
much
at
this
point
any
objection:
okay,
I'll,
just
close
that
one
now
just
try
to
clean
up
the
backlog,
all
right
community
time.
Any
questions
from
the
community
for
about
topics
that
are
not
on
the
agenda.
A
All
right
moving
on
then
so
coop
con
in
case
you
have
not
heard
it
has
been
postponed
until
June
and
July.
So
we
don't
need
to
worry
about
the
planning
at
this
point
in
time,
so
it
gives
us
a
break
for
a
presentation,
creation
and
stuff
like
that
as
things
it
does
include
these
the
day.
0
events
like
the
service
practitioner
summit
as
well.
If
anything,
does
pop
up
I'll
try
to
remember
to
mention
it
to
you
guys,
but
obviously
you
probably
the
email
is
just
the
same.
M
M
A
You
for
that
information
I
was
I.
Did
wonder
about
that?
That's
interesting,
okay,
thank
you,
Mike
I!
Guess
it
should
out
anybody
else.
Have
any
other
information
about
Kuk
on
that
people
might
want
to
know
about
all
right,
cool
mystic,
a
car
can't
I
think
it
may
had
a
call
last
week,
but
it
was
relatively
short.
We
do
have
another
plan
for
today,
I
believe
because
Scott
had
something
he
wanted
to
bring
up
today
and
also
there
is
another
PR
that
just
opened
today
that
I
wanted
to
whoops.
Did
that
again?
A
M
A
Can't
these
men
on
the
cause
or
anybody
else
from
the
work
workflow
subgroup
that
one-dimension
most
much
anything
okay,
mention
is
I,
know
that
they
are
in
the
process
of
putting
together
their
proposal
to
go
to
the
CN
CF
TOC
to
be
proposed
as
a
sandbox
project.
I
believe,
there's
a
pull
request
in
the
and
the
TOC
is
github
repo.
If
you
want
to
take
a
look
at
that,
I,
don't
think
it'd
be
surprising
to
anybody
in
this
group
has
been
kind
of
following
what
they're
doing.
A
But
if
you
have
any
comments,
obviously
please
go
over
there
and
comment
on
it
or
comment
on
it
in
the
in
the
workflow
slack
Channel.
They
watch
that
as
well.
Okay,
all
right,
let's
get
to
the
fun
stuff
discovery,
api's,
so
Mike
you're
up
first,
you
won't
look
at
the
Google
Doc
or
do
you
want
to
look
at
your
PR
I?
Think
that.
M
M
Spec
source
can
be
a
pretty
highly
variable
thing,
depending
on
the
the
events
provider,
so
it
seems
like
it
would
be
fairly
common
or
say
a
blob
storage
provider
to
have
each
directory
or
bucket
available
as
a
separate
source,
so
I
bumped
that
up
to
an
array
in
the
return
you
probably
scroll
down
a
bit
and
see
but
yeah
I
was
look
at
the
structure
of
yeah,
so
I
had
a
producer
as
a
first
order
thing,
which
would
be
a
human,
readable
string.
The
idea
is
thinking
about
UX
around
discovery.
M
You
can
imagine
somebody
building
a
CLI
or
a
UI
where,
if
you
look
at
some
of
the
notes
from
from
the
Google
Doc
from
several
weeks
ago,
talked
about
this
idea
of
discovery
funnel.
So
how
do
users
actually
come
in
and
discover
events
and
I
think
there
are
sort
of
like
two
avenues
we
think
about,
as
one
is
like
I
know
what
type
of
event
I
want
to
discover?
M
This
allows
a
provider
to
sort
of
pre
populate
this
I'm
happy
like
I'm,
happy
I
know,
people
are
familiar
with
the
Google
cloud
functions
UI,
but
it
has
a
really
nice
flow
here.
Where
it's,
you
know,
I
pick
what
service
I
want
something
I
think
I
want
to
be
sure,
goodbye,
Google
cloud,
pub/sub
and
then
I
get
a
drop-down
for
all
of
the
topics
that
I
could
be
triggered
by
and
that
allows
that
to
be
dependent
on
who's
logged
in
the.
What
am
I,
what
resources
am
I
allowed
to
see?
What
could
I
subscribe
to?
M
M
M
D
M
A
A
A
Of
I
think
I'm
still
stuck
in
this
mental
model
of
I
feel
like
there's
like
a
Elissa
static,
there's
like
a
static
query
and
then
there's
a
more
dynamic
query
and
I
model.
My
head
I
can't
figure
out
whether
I'm
right
I
need
to
convince
you
of
it
or
I'm
just
flat-out
wrong,
and
you
need
to
convince
me
of
it.
I
don't
know
yes,.
M
Saurus
I
think
is
the
more
dynamic
thing.
So,
like
the
provider
and
event
types
is
more
static.
The
one
thing
I
kind
of
went
back
and
forth
on
is
like
should
should
we
have
to
query
options,
one
which
is
basically
giving
me
the
static
thing,
don't
expand
the
sources
versus
give
me
that
I'd
anti
thing
do
expand
the
sources.
What
about
the
subject?
M
Because
it
seems
like
this
example,
TN
1,
2,
2
2,
slash
alerts
that
should
be
the
subject
and
sensors
I.
Don't
disagree
with
you
Scott,
but
that's
not
how
source
is
defined
in
the
spec
currently,
and
this
didn't
see
a
spec,
so
I
was
trying
to
lean
into
that.
I
think
you
I
think
it
is
I.
Think
there's
examples
of
both.
M
M
Think
so,
because
there
are
sources
where
like,
if
you,
if
you
grow
a
github
one,
for
example,
you
could
have
the
organ
repo,
be
the
source
and
the
subject
be
like
it,
based
a
specific
pull
request
right.
So
in
that
case
like
this
is
so,
if
you
look
at
one
of
the
other
things
I
had
in
this
source,
what
did
I
call
it
if
you
scroll
down
a
little
bit,
Doug
I
think
it's.
M
This
is
an
old
argument,
but
I
feel
like
we
need
to
go
back
to.
There
needs
to
be
some
sort
of
like
way
to
assemble
the
source
and
the
subject
into
a
single
identifier
like
you're,
showing
here
where
you
might
have
github.com
organization.
Repo
is
the
source.
Polite
pull
slash.
Id
is
the
subject.
You
want
to
talk
about
a
conical
link
to
it
and
it's
a
heck.
What
are
the
pieces
in
each
and
how
do
you
combine
them
to
make
a
single
discoverable
resource.
M
G
The
scenario
that
I
can
imagine
where
you,
where
sore
matters
so
first
of
all,
I,
think
what
we
defined
as
a
source
is
the
or
the
origin
of
the
event,
and
then
the
the
the
subject
really
describe
something
that
is
inside
of
that
orange
enough
the
event.
But
if
you
are
describing
a
discovery
API,
then
you
are
mostly
only
describing
the
origin
and
where
you
know
the
associated
and
you're
really
describing
the
Associated
subscription
manager
effectively
wait
and
gonna
get
that
event
from
now.
M
Exactly
because
the
the
the
root
source
to
its
continued
to
be
github.com
organization,
repo,
but
then
the
list
of
subjects
could
be
pole.
Id
issue
ID
comment,
ID
yeah
exactly,
but
those
would
be
I
think
different
entries
and
like
different
Discovery
docks
like
each
different
entities
because
pivoting
on
the
type
for
those
well.
G
It's
true,
but
from
a
from
a
from
a
so
yes,
there
would
be
different
entries
and
every
if
we're
referring
them
to
subscription.
It's
a
subscription
manager,
endpoints
and
those
would
also
like,
like
the
points
of
different
subscription
manager
endpoints.
But
if
you
query
for
them,
they
will
all
be
from
one
source.
G
That
is
the
organ
8
organization,
raising
events,
but
they
might
be
and
we're
just
obviously
just
you
know
speculating
here
and
get
up,
maybe
not
the
best
example
for
it,
but
they
are
from
it
from
a
particular
from
from
a
greater
source,
a
greater
context,
and
then
you
would
still
query
for
the
subject
as
a
further
discriminator.
So
the
e
connect
you.
M
This
is
the
thing
I'm
struggling
with
his
knee
like.
Could
you
actually
include
like?
Would
you
actually
expand
and
materialize
the
various
subjects
in
discovery,
because
I,
don't
I
I,
don't
think
they
exist,
upfront
I,
don't
think
I,
don't
think
you
want
to
all
right
so
like
so
that's
why
I
asked
the
question
about
is
something
like
defining
the
subject
structure
in
the
way
the
source
structure
I
have
here?
Does
that
make
more
sense
than
having
the
raw
subjects.
G
B
A
question
yeah,
so
maybe
it's
I
I,
think
it
is
right.
But
from
my
understanding
or
we
discussed
it
so
I
think
when
we
have
this
github
thing,
we
have
the
organization
we
have
to
repo
after
pull
request,
and
my
understanding
was
that
we
put
basically
including
the
PR
the
PO
request
itself
into
resource
and
then
only
the
ID
of
the
pull
request
itself.
The
particular
pull
request
they
into
the
subject
but
or
am
I
wrong.
So.
B
G
Just
from
a
platform
perspective,
but
I
can
see
there
being
a
need
for
corner
cases
like
partitioning
to
do
some
pre
filtering
also
to
do
some
pre
filter
on
the
subjects,
but
I
think
I.
Think
that's
really.
That
is
a
corner
case
like
the
the
95
percent
case
should
be
you
only
look
for
source
you
and
you
ignored
the
subject
in
the
on
the
discovery,
registration
side.
M
M
I
think
github
is
probably
a
poor
example
for
that,
because,
like
we
don't
hear,
we
talk
about
subject
as
being
ideas
of
things
which
again
are
not
known
in
advance,
but,
like
think
about,
like
a
blob
storage
kind
of
thing,
a
star
dot,
JPEG
subject,
filter
makes
a
lot
of
sense.
Yeah
I
was
gonna,
bring
that
up
like
we
understand
the
what
the
bucket
name
is.
Well,
we
don't
know
what
what's
in
that
bucket,
so
it
seems
like
we're
kind
of
falling
into
a
pattern.
D
M
D
In
this,
in
that
case,
yeah,
it's
a
good
question.
It
is
something
that
we
do
support
today,
because
you
can.
The
way
that
we
do
this
today
is
is
through
web
hooks.
You,
when
you
again
make
a
REST
API
call
through
the
API.
You
can
specify
a
status
callback
which
is
basically
analogous
to
how
we're
talking
about
got
events
that
is
completely
informational,
and
you
can
do
that
on
a
per
message
basis.
D
C
Your
hands
up,
yes,
so
maybe
another
example.
So
in
our
products,
usually
a
subject
this,
what
we
call
a
business
object,
so
say
it's
order,
or
maybe
a
customer
billing
document,
you
name
it
and
we
have
different
ways
to
identify
those
objects
and
they
might
also
exist.
The
same
object
might
exist
in
multiple
services
or
systems
and
so
for
subject
something
like
a
description
which
a
kind
of
identifier
is
used.
A
subject
for
that
event
would
be
a
helpful,
for
example,
not
the
specific
value,
but
just
what
kind
of
identifier
scheme
is
used.
A
M
M
Well,
yeah,
but
I
don't
want
to
make
assumptions
that
it's
always
an
assembly
of
source
and
subject
to
get
to
the
thing
you
just
got
because
we
do
have
data
Ref.
We
go
the
ability,
the
past
data
and
attributes
in
the
event
itself.
It's
not
like
it's
not
always
a
go
back
to
the
producer
to
ask
for
a
specific
resource
kind
of
scenario:
yeah
yeah,
the
the
cloud
of
inspect,
doesn't
help
in
this.
M
M
A
G
G
But
we're
gonna
comment
that
with
some
extra
explanation
and
that
is
who's
initiating
the
the
delivery
and
once
that's
a
consumer
initiating
it
and
once
that's
the
subscription
manager
initiating
that,
and
so
that's
going
to
be,
hopefully
helping
to
clarify
this,
and
so
but
the
sips
respect
that
the
part
of
the
subscription
documents
ended
up
being
much
longer
than
I
thought.
So
this
is
about
me
not
being
able
to.
You
know,
get
the
homework
done
between
Tuesday
and
I'm.
Sorry
about
that,
okay.
A
A
Okay,
in
that
case,
thank
you
comments
and
everybody
else
in
the
group
I'm
looking
forward
to
the
PR
okay,
one
question
for
people:
let
me
go
check
here
so
Mike,
you
created
it
as
a
top
little
document,
which
obviously
makes
sense
as
of
right
now
at
some
point.
As
long
as
we
keep
these
specs
in
the
same
repo,
we
are
probably
gonna
want
to
think
about
restructuring
the
repo
itself
to
have
directories
and
stuff
just
want
to
check
people.
Do
you?
A
G
M
A
Yeah,
no
no
I'll
go
off
and
think
about
positive,
restructure
of
everything,
and
then
we
could
figure
I
worried
you
guys
stuff
go
later.
Okay,
in
that
case
last
chance,
any
questions
comments
about
the
overall
talk,
whether
it's
clement
section
or
does
everything
in
general,
you
all
right
cool!
Thank
you.
In
that
case,
let's
go
to
pr's
okay.
So
there
was
a
question
about
if
I
can
even
remember
this
thing
for
one
second,.
A
So
I
know
I'm
starting
to
come
up
to
speed,
but
I
feel
like
I,
still
know
next
to
nothing
about
I've
got
so
I'm
gonna
hand
you
to
come
with
you
guys,
but
this
seemed
okay
to
me,
but
for
anybody
who
you
actually
play
with
kafka
lat,
do
you
guys
have
any
opinion
on
this?
Is
this
something
that
we
need
actually
that
we
need
to
actually
specify,
or
was
it
okay
before.
G
G
A
G
J
G
J
Finally,
called
currently
the
when
you
set
another
you,
the
adders
inside
the
JVM
client
are
represented
as
at
least
yeah,
not
as
a
matter
the
list
as
record
data
I,
think
it's
the
name
of
the
object
and
it's
a
key
byte
array
and
value
battery.
So
she
spider
is
yeah
I,
think
maybe
I
should
check,
but
I
record
me
that's
how
it
works
and
and
for
example,
this
basically
came
out
when
I
was
implementing
the
calf
binding
for
the
cloud
events
go
SDK,
so.
D
G
G
A
Sorry
I'm
you,
let's
give
everybody
a
week
to
think
about
it.
I
don't
want
to
rush
it,
and
the
must
is
the
thing
that
worries
me.
So
I
want
everybody,
take
a
look
at
it
or,
if
you
know
about
the
stuff,
take
a
look
at
it
and
if
you
have
any
concerns
comment
before
next
week's
call,
some
fear
all
right.
Thank
you.
Everybody
all
right.
A
This
PR,
it's
my
I
came
here
exactly
where
it
was,
but
somewhere
somebody
had
a
question
about
how
to
discover
whether
an
incoming
message
is
actually
a
cloud
event
and
obviously
when
it
is
a
structured
cloud
event,
it's
easy
because
the
mime
type
tells
you
that
really
content
like
better,
tells
you
that.
However,
it
wasn't
clear
what
to
do.
If
it's
a
binary
message
I
had
you
know
whether
it's
a
cloud
event
then,
and
the
spec
never
actually
says
so.
A
What
I
thought
about
doing
was
adding
some
text
along
these
lines
here,
which
basically
says
if
it's
binary
and
the
four
required
headers
are
present.
Then
it's
a
cloud
events
now
that
you
can't
be
a
hundred
percent
guarantee
to
that,
because
we
can't
stop
somebody
from
just
randomly
using
our
headers,
but
not
claiming
that
they're
compliant
cloud
of
inspect,
for
some
reason
that
just
could
be
borrowing
ours.
So
what's
out
of
our
domain
to
actually
mandate,
something,
like
you
know,
don't
use
our
headers
unless
you're
a
cloud
event
spec.
We
can't
say
that.
A
That's
why
I
say
things
like
it
would
be
reasonable
for
a
receiver
to
assume
that
I
think
that's
the
best
kind
of
guidance
we
can
provide.
So
if
you
guys
take
it
get
a
chance.
Please
take
a
look
at
this
see
if
the
text
sounds
right,
if
you
don't
like
the
entire
idea
at
all,
obviously
say
that
as
well,
but
if
you're,
okay,
with
this
general
direction
for
the
text,
then
I'll
make
similar
changes
to
the
other
protocols.
A
But
I
wanted
to
start
with
HP
one
to
see
how
people
thought
about
it
in
general,
okay
and
Francisco
to
your
question.
I
think
maybe
I
need
to
clarify
this
I
say
mandatory
fields,
I'm
talking
about
the
mandatory
cloud
event
attributes
so
there
and
there's
four
of
them:
spec
version,
one
of
the
source
type
and
one
of
upon
I
camera.
What
it
was,
those
those
what
I
mean
by
required.
M
A
That's
good
yeah,
it's
funny.
Originally,
the
text
in
here
only
talked
about
the
spec
version
field
and
then
I
couldn't
sleep
last
night,
so
I
started
thinking
about
this
from
some
reason
and
I
realized
that
technically
it
shouldn't
just
be
that
one
field
that
actually
should
be
all
for
base
since
they're
all
required
fields,
and
that
way
you
can
say
well,
if
you
don't
have
all
four
and
you
only
have
three
of
them.
Well
then
you're
not
complying
to
the
spec.
Therefore
you're
not
a
cloud
event,
and
that
was
my
original
thinking.
M
J
A
M
M
A
Okay,
well,
obviously,
I'm
I'm
always
open
to
the
wording
to
wording
changes.
So
if
you
think
the
wording
here
needs
to
change
them,
you
know,
but
it
doesn't
sound
like
it
disagrees
with
the
general
direction.
It's
more
a
question
of
four
versus
one
attribute
and
maybe
some
wording,
but
you
know
you
don't
think
about
it
right
now
on
the
call.
A
But
yeah,
if
you
think
you
have
some
you're
gonna,
have
some
comments
on
there.
I
would
appreciate
comments
sooner
rather
than
later,
because,
as
I
said,
I
would
like
to
make
similar
changes
to
the
other
transport.
Specs
I
thought
about
possibly
putting
this
into
the
main
spec
itself,
but
I
thought
the
text
might
be
different
or
might
be
transport
specific.
That's
why
I
stuck
it
in
here,
but
if
you
guys
think
it
might
be
better
suited
in
the
main
spec
itself,
I
can
try
to
fit
it
in
there.
A
M
A
A
A
M
Yeah
I
think
that's
right.
The
end
result
is
that
these
are
both
of
valid
examples
but
they're
not
equivalent,
because
the
middle
example
there
that
it's
a
string
of
serialized
JSON
object
as
a
JSON
string.
The
third
example
is
fubar
object,
as
if
JSON
object,
mm-hmm,
though
they
have
the
same
data
but
they're
not
equivalent.
All.
A
J
Yes,
I
think
it's
just
maybe
some
that
were
doing
which
I
found
while
I
was
implementing.
The
calf
specification
is
that
inside
the
curve
combining
specification,
it
states
that
there
should
be
a
key
assumption.
While
then
I
open
the
link
of
the
partitioning
extension
specification
and
the
name
is,
and
the
name
of
the
extension
is
partition
key.
So
that's
that's
not
clear.
That's.
E
A
We're
saying
he's
Francisco
was
saying
that
in
the
Kafka
spec
we
used
the
word,
or
we
talked
about.
In
extension,
key
Irene
essentially
called
key
pointing
to
the
partitioning
extension
spec,
but
in
the
Perdition
extension
spec
it's
actually
called
partition
key,
not
just
key.
So
there's
any
consistency
in
the
wording
for
the.
K
A
J
A
All
right
last
one
this
is
I-
was
gonna,
bring
this
up
in
the
SDK
call.
But
if
anybody
has
any
question
or
comments
on
this,
my
just
want
to
bring
it
up
quickly.
There
was
a
question
in
the
SDK
dot
MD
file
that
talks
about
what
we
expect
of
SDKs
and
it
basically
says
you
know,
support
ongoing
change
to
cloud
even
spec.
Obviously
you
know
try
to
keep
up
to
it,
but
somebody
asked
a
question
or
what
that
actually
means
right.
Does
it
mean
every
single
version?
There
is
single
version
or
release
candidates.
A
Point
releases
major
releases
whatever
so
I
tried
to
make
clear
that
it
be
nice
if
everybody
supported
at
least
the
latest
and
n
minus-1
major
release
and
then
for
each
major
release,
we're
only
going
to
ask
them
to
at
least
support
the
very
latest
point
release
and
that
release
candidates
are
not
required,
but
strongly
encouraged.
We
don't
understand
to
talk
about
that
now.
A
K
A
K
K
A
J
A
A
A
A
M
So,
basically
we're
we're
looking
at
the
the
work
on
bindings
exposed
a
lot
of
performance
improvements
that
can
be
done.
If
you
don't
delegate
all
the
way
down
to
the
conical
event,
which
is
something
we
want
to
promote
in
other
projects,
so
we're
gonna,
rework
the
SDK
to
make
it
easy
to
be
able
to
be
an
integrator
at
that
level.
So
if
you
would
like
to
be
a
function
and
consume
events,
it
works
for
that.
M
If
you
would
like
to
be
kind
of
middleware
and
receive
like
half,
parsed
message:
objects
that
aren't
there
their
events
internally,
but
they're,
not
all
the
way
exploded
out,
that's
possible,
and
then
you
can.
You
know
forward
it
on
to
the
next
transport
hop
so
like
doing
middleware,
fan-out
or
filtering
and
fan-out.
So
you
have
access
to
the
attributes
and
then
we're
gonna
make
it
possible
for
somebody
that
would
like
to
interact
with
their
transport
or
the
protocol
directly.
M
So
like
the
AWS
use
case,
and
they
just
want
access
to
be
able
to
marshal
the
event
in
and
out
of
some
JSON
form
and
that'll
be
possible.
So
we're
we're
trying
to
service
these
kind
of
like
three
main
users,
this
sdk.
So
it's
picked
the
format
in
which
you
want
to
see
the
data.
It's
it's
basically
you're
in
this
sliding
scale
you're
giving
up
or
taking
over
control
over
the
protocol
interesting.
M
So
it
like
a
function,
consumer
point:
you
don't
really
care
how
it
got
to
you,
you
don't
even
care
what
protocol
came
on.
You
just
care
that
as
an
event
at
the
at
the
middleware
level.
You
really
care
about
optimizing.
The
usage
of
the
protocol,
so
that
you
can
do
things
like
understand
how
your
partition
keys
in
Kafka.
Are
you
in
working
and-
and
we
don't
have
to
like
plumb
all
that
data
through
the
SDK,
because
it's
too
cumbersome.
M
So
the
work
here
that
sir
slinky
and
I
are
working
on
is
like
trying
to
make
this
easier
so
that
there
can
be
an
optimized
usage
of
the
SDK
or
it
gets
out
of
your
way,
and
you
can
do
all
the
things
you
do
today,
but
still
gives
you
the
ability
to
take
your
event
and
push
it
on
to
the
wire,
but
not
drop.
The
use
case
of
life
make
its
do
super
stupid,
easy
or.
A
O
M
A
A
All
right
cool,
thank
you,
so
I
went
back
and
looked
at
some
of
the
more
recent
old
meetings
to
to
make
sure
I
was
I
pulled
out
some
of
the
action
items
because
I
kept
feeling
like
we
were
forgetting
to
do
something
and
I
came
across
one
that
assigned
to
me.
That
said,
make
sure
we
documented
the
leads
for
each
SDK,
which
conceptually
sounds
good.
So
people
know
who
to
polka
like
they
have
specific
questions.
A
However,
before
I
I
wanted
before
I
was
gonna
go
off
and
do
that
I'm
gonna
double
check
and
make
sure
that
we
really
did
want
to
do
that.
Because
do
people
really
want
to
get
pinged
directly
about
stuff,
or
do
we
want
to
add
text
to
each
readme?
That
says,
if
you
have
a
question
about
this,
don't
hesitate
to
open
up
an
issue
that
way
it's
not
pointed
I,
won't
particular
person.
It's
to
the
group
itself.
I
have
a
terrible
idea.
What's
that?
What.
M
G
M
A
J
N
This
exactly
the
this
action
items
started
because
we
were,
we
didn't
know
what
SDKs
supported,
1.0
and
Doug
had
to
contact
everybody.
We
have
no
idea
who
to
come
to
yeah
did
release
indicators.
The
sharpest
decay
were
very
well
now,
not
undocumented.
The
JavaScript
SDK
to
I.
Think
Fabio
was
working
on
that
rather
public
and
but
the
rest
of
them
were
a
bit
unmaintained
or
less
than
thing.
To
put
it
nicely,.
F
J
A
M
I
already
voted
I
actually
offense,
so
we
we
were
talking
to
a
client,
and
this
was
4k
native
the
client
because
they're
a
publicly,
they
have
like
some
government
regulation
and
they
were.
They
can't
talk
to
us
using
slack
because
it's
a
to
free
form
of
immediate
and
it's
not
audited.
So
the
only
way
they
can
interact
with
us
is
through
email.
A
So
it
seems
to
me,
though,
that
the
amount
of
traffic
we
have
right
now
is
relatively
small,
even
for
something
as
poplars
to
go
SDK
so
I.
That's
why
it's
in
threes,
where
I'm
a
little
nervous
about
one
knowing
less
per
SDK?
What,
if
we
could?
We
start
with
1
million
less
for
all
this
decays
and
then,
if
one
particular,
if
one
particular
one
gets
busy,
we
can
look
to
fork
it
to
its
own.
Yes,.
A
A
G
G
G
M
B
G
Yeah
we
we
have
so
so
for
c-sharp,
since
we
that's
our
home
language
at
Microsoft,
so
to
speak,
and
we
have
so
lots
of
our
customers
are
using
it
and
we
have
had
customers
who
have
been
using
cloud
events
with
Eventbrite,
where
we
supported
zero
one
in
the
product
and
we
didn't
support
anything
in
between.
But
then
we
so
far
is
support.
100
I
have
to
think
about
what
what
the
repercussions
of
cutting
it
are,
but
yeah
customers
shouldn't
gone.
G
M
J
M
A
A
M
A
Yes,
but
just
you're
speaking
abstractly
I
agree
with
you,
but
concretely
do
we
want
to
say:
0.3
is
a
special
case
and
because
n
minus
one
doesn't
exist,
we're
gonna
say
you
should
support
0.3
as
long
as
N
equals
one
point:
oh
yeah,
maybe
I
think
you
should
remove
that
word
major
and
just
say
releases
well,
the
problem
was
I
at
that
point.
Well,
what
is
a
release
right?
Is
it
one
point
one
versus
one
point:
oh
I,
don't
think
so
mm-hmm
right!
A
A
A
M
M
A
So
what's
interesting,
is
you
phrased
it
nicely
abstractly
that
that's
good,
but
realistically
we
already
say
that
here
right
and
the
only
reason
that
you
actually
need
that
others
sentence
they
just
said
is
because
of
the
1.0
situation,
so
it
may
be
better
for
an
understanding
perspective
to
not
be
coy
about
it
and
to
say
look.
1.0
is
a
special
case.
It
is
highly
recommended
that
you
also
support
0.3,
yeah
sure,
as.
A
M
A
M
J
M
This
one-
maybe
oh
boy
here
we
go
hold
on
okay,
so
I
made
a
thing.
It's
called
cloud
events
you
can
install
it
there's
instructions,
the
the
idea
is
that
you
could
have
this
like
canned
set
of
yeah
mole,
that's
encoded
as
the
event
and
then
send
it
out
to
some
target,
which
is
pretty
interesting,
but
it
also
has
a
mode
where
you
can
say
cloud
ovens.
M
M
Connect
Joe
because
some
idiot
made
a
typo
so
now
I
can
send
with
cloud
events
and
then
over
here
the
cloud
events
conformance
tools,
also
listening,
and
it
doesn't
do
any
like
major
data
processing.
It
just
dumps
stuff
out
and,
as
you
can
see
it
doesn't
do
it
exactly
right
and
then
maybe
there's
some
bugs
in
here,
because
it's
very
very
little
code
you
can
also.
M
The
thing
that's
interesting
is
that
this
is
a
stream
of
yeah
Mille,
it's
written
to
to
the
standardout.
This
is
written
to
standard
error,
so
you
can
pipe
this
the
output
of
listen
to
a
file
and
then
have
a
stream
of
events
that
it'll
try
to
for
you
in
the
next
round.
If
you,
if
you
so
choose
so
you
can
do
a
lot
of
cloud
events
invoke
and
invoke,
takes
a
target
and
a
file
and
it'll
the
file
can
be
a
directory
and
you
can
recurse
that
directory
structure
in
case
you
want
to
do
that.
M
A
M
Conformance
thought
was
that
you
could
you
produce
this
file
that
you
listen
on
and
then
you
compare
that
to
what
you
sent
and
if
those
two
things
are
the
same
like
by
a
diff,
then
you,
you
are
sending
what
you
are
receiving
or
your
so
you're
receiving
what
you're
sending
at
least
you
think
you
are
okay
that
helps.
Thank
you
alright.
So
the
thought
was
that
this
is
a
double-ended
thing
and
it
would
go.
You
know
it
invoke.
M
And
then
some
black
box
you're
testing
and
then
the
black
box
says
supposed
to
send
another
HTTP
request
to
this.
Listen
and
so
invoke
is
taking
in
Y
amal
some
set
of
gamal
and
then
listen
produces
some
yeah
mold
and
at
the
end
of
the
test
you
can
compare
what
the
invoke
Yamma
looked
like
and
what
the
listen,
oh
god
I'm
sorry
I
need
to
write
a
tool
that
helps
you
do
that
diff
and
see
if
it
passed,
because
there's
some
extra
garbage
that
sticks
in
here
for
you
mm-hm.
So
those
are
transport
extensions.
J
Anyway,
can
I
create
a
full-fledged
TCK
from
this,
because
that's
something
that
I
would
love
to
have
for
for
the
Rastas
decay,
because
now
we're
starting
so
I
mean
it's
it's
a
command-line
tool,
so
you
can
interact
with
it
yeah.
What
I
mean
is
that
that's?
Do
you
feel
that
some
point
we
could
provide
scripts
or
radio
make
already
made
yum
output
yeah
modes,
so
right.
M
V10,
you
see
I
mean
Frank,
so
I
kind
of
cheaped
out,
but
you
see
what
the
the
minimum
version
of
what
I
think
a
valid
Cloud
event
would
look
like
at
the
minimum
level.
This
is
like
testing
that
emojis
work
and
all
this
stuff,
and
so
you
can
actually
actually
we'll
try
it
now
cloud
events
in
both
HTTP.
M
8080
and
then
f
this
file,
and
so
it
goes
and
reads
that
file
interprets
it
back
into
an
object.
It's
very
simple
code,
there's
not
a
lot
of
logic
here
and
then
the
listen
tool
dumps
out
what
I
got,
and
so
you
know
there's
a
couple.
Things
looks
like
it's
not
actually
doing.
This
should
be
it
actually,
that's
fine.
This
one.
J
M
The
idea
was
that,
like
you,
have
this
set
of
conical,
JSON
or
conical
yamo
that
you
write,
but
it
also
helps
you
produce
it,
and
then
it
helps
you
send
it
as
a
blob.
But
you
can
also
like
poke
at
things
that
are
running
and
so
like
as
I'm
testing
with
it's
actually
really
useful
for
the
that
changes
for
the
go
SDK,
because
I
know
that
this
is
an
alternate
implementation
that
mostly
works.