►
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
B
A
C
A
A
B
A
Okay,
so
starting
off
with
Andrew
Locke
today
he
is
looking.
This
is
kind
of
a
deep
dive
into
asp
net
core
app
meta
package.
What
I
really
like
with
this
we've
definitely
talked
about
this
in
the
past.
A
Mian
has
gone
through
this,
but
kind
of
this
is
nice
because
he
talks
about
the
whole
history.
You
know
talking
about
asp
net
core
one.
Oh
you
know
we
had
so
many
packages,
then
we
had
with
asp
net
core.
A
We
had
a
meta
package
and
we
had
a
runtime
store,
but
he
talks
about
some
of
the
issues
that
came
up
with
that
you
know
ever
growing.
Runtime
stores
other
problems
with
with
versioning
it's
so
then
talking
about
here
goes
into
shared
frameworks
and
talks
about
is
how
there's
the
is
peanut
core
all
meta
package
and
the
asp
net
core
dot
app
meta
package,
and
talking
about
you,
know
how
specifically,
as
peanut
core
app
works.
A
Also,
you
know
that
the
kind
of
TL
DR
is
reference
asp
net
core
dot,
app
in
your
in
your
apps.
This
is
also
this
is
by
default
in
the
in
the
templates.
It
points
to
that,
and
so
you
know
kind
of
talking
about
also
how
the
dependency
ranges
move
from
these
move
to
exact
version
requirements.
So
kind
of
you
know
some
simplicity
and
also
serviceability
and
kind
of
eliminating
some
of
the
package
versioning
issues
from
previous
versions,
so
cool
to
see
kind
of
as
he
walks
through
the
kind
of
history.
What
happened
in
the
past?
A
A
It
is
a
compact
way
of
you
know
packing
data,
it's
a
it's
a
message,
transport
format,
and
so
here
he's
talking
about
bringing
in
bringing
a
message
pack
as
a
package
and
then
using
that
I'm.
Sorry,
you
know
kind
of
walks
through.
This
is
a
relatively
straightforward
kind
of
quick
sample,
but
yeah
it's
all
kind
of
there
and
of
course,
there's
some.
You
know:
there's
a
link
to
sample
code
there
to
atom
store,
he's
continuing
a
series
on
asp
net
core
web
hooks.
This
one
is
on
running
the
get
github
webhook
locally.
A
What's
interesting
here,
you
know:
there's
the
standard
kind
of
web
hook
set
up
stuff.
He
raymond
you
an
issue
which
is
that
they,
you
can't
run
this.
You
can't
run
this
all
locally
there.
You
can't
point
to
a
local
host
endpoint,
so
he's
using
an
brock
for
this
and
and
then
setting
it
up
for
for
the
port
forwarding
to
get
that
to
work
so
n
grok
is
his
endpoint
he's
able
to
test
that
out
with
its
hub
web
hooks,
and
then
this
forwards
to
localhost,
allowing
him
to
go
through
and
and
test
this
out
locally.
A
C
A
What
I
wanted
and
boof
this?
For
me,
this
is
just
kind
of
a
quick
little.
You
know
thing
to
be
aware
of
slash,
I,
guess,
kind
of
exciting
thing.
This
is
Steven
halters,
pointing
out
that
Kestrel
HTTP
server
is
switching
over
to
defaulting
to
the
manage
socket
transport.
So
you
know
that
previously
it
was
defaulting
to
libuv
and
now
this
is
defaulting
to
the
manage
socket
transport.
So
that's
kind
of
neat,
so
we've
done
the
flip
flop
once
but.
B
A
A
Okay,
this
is
from
Steven
Gordon
as
Steve
Gordon
he's
talking
through
dependency
injection,
registering
generic
types,
definitely
useful
as
you're
registering
generic
types
in
asp
net
core
apps.
So
this
is
he
talks
through
you
know.
If
you're
registering
a
generic
implementation,
then
what
you
want
to
be
doing
kind
of
cutting
to
the
chase
here
is
using
type
of
and
then
that'll
allow
you
to
register
a
generic
type
for
an
interface
so
straightforward.
A
But
this
is
the
kind
of
thing
where
you
know
you
could
get
stuck
on
if
you,
if
you
weren't
aware
that
Brady
gaster
here
he's
got
an
example
and
the
demo
application
using
semantic
UI
with
asp
net
core
razor
pages
so
semantic
you
eyes,
you
know
similar
conceptually
to
something
like
bootstrap
but
as
a
friend
framework
more
based
on.
So
it's
bootstrap
is
very
much
there's
a
lot
of
classes,
there's
tons
of
divs
everywhere
and
rath
divs,
and
that
sort
of
thing,
if
you
really
like
semantic
HTML.
A
A
Actually,
it's
does
say:
it's
locked,
I'm,
confused,
okay,
so
semantic
UI
for
so
semantic
UI.
Here
he
kind
of
walks
through
using
that
this
is
so
he's
installing
that
via
NPM-
and
this
is
a
you
know-
just
a
kind
of
a
sample
application.
So
again,
some
antique
UI
kind
of
more
based
on
the
markup
is
very
much
like
using
the
HTML
elements
themselves.
A
So,
instead
of
divs
and
divs
and
divs
with
a
bunch
of
bootstrap
classes,
it's
it's
more
kind
of
a
you're
going
to
have
things
like
you
know,
sections
and
and-
and
you
know,
kind
of
your
standard
sort
of
things.
This
is
nice
to
see
with
a
hair,
let's
just
pop
over
into
one
of
these,
so
you
know,
for
instance,
P
tags
instead
of
div
with
a
class
of
something
or
something
rather,
and
if
we
look
at
the
layout
we'll
see
that
as
well,
it's
kind
of
more
you
know
there
are.
A
There
are
divs,
but
you're
also
going
to
have.
You
know,
in
general,
things
like
sections
and
footers
and
stuff
like
that:
alright
Fabian
showing
a
build
pipeline
with
angular
for
asp
net
core
apps
using
visual
studio
team
services.
So
this
is
setting
up.
You
know
the
full
build
pipeline.
It's
relatively
straightforward
with
things
like
asp
net
core,
as
you
get
into
the
kind
of
interesting
kind
of
call
out
thing
here
is
there's
also
the
angular
setup
here.
So
he's
got
the
angular
build
process
included
in
here.
A
A
So
you
talks
through
you
know
what
is
a
tag
helper,
how
it
differs
from
HTML
helpers,
and
so
here
you've
got
things
like,
for
instance,
a
you
know,
a
HTML
helper,
and
we
want
to
go
through
and
convert
to
tag
helpers.
So
he
shows
you
know
how
they
work
and
and
kind
of
talk
to
you
through
doing
that
and
he's
got
an
example
using
using
kendo
UI
for
that,
so
that
is
it
so
I'm
going
to
pop
back
over
to
you
alright,
so
I
am
done
with
my
links
for
the
week.
C
Yeah
we've
been
working
on
the
asp
net
core
module
for
a
while
now,
and
so
just
you
know,
maybe
let's
have
a
look
at
a
brief
history
way
back.
You
know
beta
aid.
Before
we
one
org,
we
had
this
server
called
Helios
that
allows
you
to
host
inside
of
is
and
then
somewhere
along.
We
can
did
we
said
we're
gonna
go
we're
gonna
bet
we're
going
all-in
on
Castro
and
we
built
a.
C
We
we
did
feel,
though,
that
it
was,
you
know,
castles
matured
enough
and
maybe
it's
time
to
revisit
running
asp
net
core
in
in
your
is
worker
process.
So
we've
been
toying
around
with
that
fact.
So
maybe
I
can
you
know,
share
my
screen:
pull
up
a
diagram
just
to
show
people
like
a
brief
idea:
yeah,
okay,.
C
I
just
want
to
bring
out
this
diagram
on
the
Left,
where
it
says,
ANSI,
I'm
out
of
process
is
how
the
asp
net
core
module
works
today,
so
requests
come
in,
they
come
into
the
is
worker
process
and
the
NCM,
which
is
a
native
module,
Anaya's
proxied
the
requests
over
using
one
HTTP
and
it
spawned
the
backend
process.
That
was
dotnet,
I
XE,
and
that
was
the
process
that
loaded
the
core
CLR,
and
that
was
the
process
in
which
your
application
and
your
code
ran.
C
But
now
we've
been
looking
at
a
new
model,
we've
been
looking
at
an
in
proc
model
and
the
idea
is
an
cm.
Would
lowered
the
core
CLR
in
this
in
the
is
worker
process
in
your
code
would
run
in
the
same
process.
So
it's
it's
no
longer
kestrel
as
your
server,
which
is
being
reverse
proxy.
It's
really
is
serving
as
your
server.
C
So
yes,
this
is
what
I
wanted
to
show.
Besides
the
you
know,
change
in
architecture,
the
the
most
exciting
thing
about
this
change
is
it's
faster,
so
we've
been
doing
some
birth
tests
in
our
observations
right
now,
it's
somewhere
between
four
and
six
times
faster.
So
if
you
weren't
excited
about
it
before
you
should
be
now
so,
like
I
said,
we
have
a
couple
motivations
for
doing
this
port
was
definitely
one
thing.
C
So
we
figured
so
we
decided
look
into
like
if
we're
anyways
doing
this
improv
work.
What
can
we
do
to
make
this
part
better?
How
can
we,
you
know,
perhaps
decouple
it
from
is-
is
as
much
as
possible
and
how
can
we
allow
ourselves
to
iterate
on
this
faster
and
you
know,
deliver
features
with
the
faster
cadence,
so
the
solution
that
we've
landed
on
for
that
and
john
feel
free
to
interrupt
me
at
any
point.
I
don't
want
to
go
into
a
monologue
here.
Sure.
A
C
So
the
solution
that
we
will
ended
on
here
is,
unlike
in
the
past,
where
we
shipped
a
single
dll
or
a
single
global
module.
Now
we've
split
up
the
SP
nut
core
module
into
two
separate
components:
the
two
components
which
are
the
shim
and
the
request
handler.
So
the
shim,
as
the
name
suggests,
is
just
a
lightweight
shim
and
he
will
continue
to
ship
via
the
serving
server
hosting
bundle.
It
will
continue
to
be
globally
installed,
but
the
shim
doesn't
do
any
of
the
heavy
lifting
all
the
heavy
lifting
is
done
by
the
request
Handler.
C
So
we
have
a
you
know:
strict
contract
between
the
shim
and
the
request
handler.
But
now
the
request
handler
is
no
different
from
any
other
nougat
package.
You
can
reference
it
or
we're
also
shipping
it
as
part
of
the
same
shell
framework.
It's
in
the
meta
package,
so
going
forward
different
apps
can
bring
in
different
implementations
of
the
request
handler.
So
this
is
starting
to
one.
So
let's
say
you
have
a
to
one
app
on
your
machine
and
at
some
point
in
the
future
tutu
comes
out.
C
You
can
now
reference
the
new
request
handler
directly
from
your
app
and
you
can
have
two
apps
on
the
same
server,
one
running
a
to
one
version
of
the
request
handler
and
another
running
the
to
two
version
of
the
request.
So
we
think
you
know,
in
addition
to
allowing
us
to
ship
with
a
higher
cadence.
It
also,
you
know,
reduces
the
chance
of
things.
Breaking
and
I'm
really
excited
about
this.
C
A
C
So
what
I
have
in
my
machine
right
now
is
I,
have
a
preview
build
of
Visual
Studio,
so
this
should
be.
Don't
quote
me
on
this,
but
I
believe
this
bill
is
out
later
this
week.
This
is
the
15.7
preview
to
build
and
what
it
does
have
is,
it
does
add,
support
for
trying
out
this
new
in
process
model.
We
we
hadn't
shifted
in
in
in
the
preview
one
release
of
2.1
preview,
one
of
asp.net
we
hadn't
shipped
it
globally.
C
A
B
C
Think
yeah,
so
that
deployed
as
a
button
for
folks
were
watching
along
and
wanna.
Try
this
you
know,
go
ahead
and
hit
that
button.
That's
gonna
provision,
a
VM
for
you,
that's
gonna!
You
know
in
set
out
by
as
web
deploy
installed
the
latest
ANSI
M
bits.
So
you
know
just
about
when
we
finish
this
show.
You
should
be
all
set
up
with
the
new
machine
to
go.
Try
this
with
people.
A
B
A
C
A
A
C
So
so,
like
I
said,
I'm
using
a
a
preview,
build
of
Visual
Studio,
the
stuff
that
I'm
showing
is
coming
out
in
the
15.7,
but
if
you
do
build,
which
don't
quote
me
on
but
ships
sometimes
this
week
and
and
it
adds
support
for
allowing
you
to
choose
between
in
Prague
now
to
Prague.
So
the
good
thing
is.
This
is
purely
or
deployed
deployment.
I'm
decision,
so
you
don't
have
to
ahead
of
time,
choose
whether
you
want
your
application
to
be
in
process
or
not.
C
C
What
I
do
want
to
show
you
is
this
new,
so
I'm
on
the
debug
tab,
right
and
I'm,
looking
at
my
iose
Express
debug
profile
and
there's
this
new
drop-down
that
you
wouldn't
have
seen
before,
that
allows
you
to
choose
your
hosting
model,
and
so,
if
I
go
ahead
and
choose
so
the
default
today,
the
default
is
still
out
of
process,
and
you
know,
based
on
feedback
from
folks,
try
it
out
based
on
results
of
our
perfect
restaurants.
You
know
we're
looking
and
hoping
to
make
the
switch
to
default
in
proc,
but
we
haven't
yet.
C
C
You
have
your
eyes:
Express
XE,
launch
another
back-end
process,
dotnet
directs
e,
and
that's
what
we
see
so
there's
nothing.
Fancy
about
that.
I
will
switch
over
to
another
app
that
I
have
here,
because
I
made
one
small
change
to
it.
I
did
this
added
this
route
process
name
and
all
it
does.
Is
it
just
gets
the
current
process
name
and
says
hello
world
from
process
name
so
and
in
this
example,
I
can
quickly
show
you
I'm
gonna
first
run
with
hosting
model
in
process.
Let's
go
f5.
C
C
And
I
will
show
you
that,
right
again
it
says
hello
world
from
dragnet.
So
this
is
the
art
of
proc
model
as
contrasted
to
the
in
proc
one
that
I
showed
before
and
for
folks
were
not
keen
on
this
experience,
there's
no
real
magic
going
on.
If
I
open
the
launch
settings
JSON
file
that
you
may
or
may
not
have
seen.
It
just
adds
this
new
property
in
CM
hosting
model,
and
you
can
easily
swap
between
okay.
A
C
Interesting
bring
up
the
bill.
Processor
there's
actually
a
cleaner
way
to
do
that.
So
what
I
was
showing?
You
was
just
your
launch
settings,
which
is
just
your
debug
profiles.
If
you
will
right,
if
I
go
ahead
and
open
my
CS
Braj
there's
this
new
project
property
that
says
the
asp
net
core
module
hosting
model-
and
this
is
what
you
really
want
to
set,
because
when
you
go
run,
dotnet
publish
in
the
command
line
you,
your
publish
output
will
have
a
generated
web
config.
C
C
So
I'm
gonna
open
this
is
the
generated
web.
Config
then
doesn't.
If
you
can
see
my
screen,
you
see
this
there's
this
new
attribute
called
hosting
model
on
the
SP
that
core
element-
and
it
is
currently
set
to
in
process,
because
that
was
the
project
property
I
specified
at
the
time
of
publishing.
Now,
of
course,
I
can
override
it,
as
you
know,
run
time
as
a
runtime
decision.
I
don't
have
to
choose
a
while,
deploying,
but
ideally
you'd
set
this
to
whatever
you
want
and
the
way
we
plan
to
control.
This
is
based
on.
C
A
Reminder
because
sometimes
this
can
be
a
little
confusing.
Is
that
there's
the
they're
like
web.config
used
to
be
the
central
kind
of
place
where
you
said
all
the
configuration
right
and
that's
really
kind
of
moved
over
to
things
to
beam
in
in
the
SP
net
configuration
map,
settings
etc,
but
for
I
is,
is,
is
still
configured
through
web
config
right
right.
C
So
if
we
actually,
you
know,
go
back
and
look
at
that
problems
filed
you
can
see.
This
is
pretty
much
looks
like
the
standard
web
config
for
any
SP
nightcore
app.
It
doesn't
really
do
much
except
add
a
handler,
that's
pointing
into
the
asp
net
core
module.
There's
no
other
app
configuration
here
and
you
you
never
see
that
in
your
web
config.
The
only
thing
this
is
telling
is:
is
hey,
go
use.
This
module
got.
A
C
C
C
So
you
know,
I
was
telling
you
I,
headed
out
with
process
name
that
said
hello
world
from
process.
The
only
reason
I
did
that
is
because
I
wanted
the
the
default
app
response
to
be
the
same,
no
matter
what
hosting
model
I
ran.
This
is
what
most
people
would
do
and
I've
done
what
we
do
in
our
you
know,
benchmark
app,
which
is
I.
Have
you
know,
by
the
way
that
already
has
your
response
and
I
don't
even
have
to
compute
the
land,
so
literally
all
I'm
doing
is
just
writing
this
byte
array
back.
C
C
C
I'm
gonna,
give
it
eight
threads
and
I'm
gonna
point
it
oops.
So
first,
let's
go
ahead
and
run
the
out
of
prog
app
and
see
what
kind
of
requests
throughput
I
get.
So
on
my
local
machine
and
again
I
know
I,
don't
want!
You
know
people
to
kill
me
for
this
and
no
it's
an
unscientific
test,
but
you
can
see
the
difference
even
in
this.
Basically.
A
C
So
so
here's
what
I'm
seeing
I'm
seeing
around
close
to
10,000
requests
per
second
hey.
Somebody
said
this
is
the
baseline
and
now
I'm
going
to
try
my
in
in
brach
version.
Let's
go
ahead,
run
this
as
well
and
I.
Think
even
on
this
machine
and
despite
me
doing
all
sorts
of
fun
stuff
like
sharing
my
screen
it
should.
You
should
still
see
the
difference.
Ok,
so
we
don't
quite
see
the
four
to
six
times
the
throughput
that
we're
seeing
in
our
birth
test,
but
I
am
seeing
comfortably
twice
the
throughput
in
my
machine.
B
A
C
A
C
C
A
Cool
a
few
other
questions,
and
so
another
one
from
Dane
is:
how
does
this
compare
to
Kestrel
directly?
So
this
is.
This
is
a
from
the
guidance
and
everything.
That's
it
is
important
to
keep
in
mind.
Kestrel
is
has
been
as
a
is
peanut
core
it's
been
hardened
so
like,
but
really
we
do
still
recommend
the
guidance
does
say
you
should
put
a
you
know
full
web
server
in
front
of
it
normally
so.
C
I,
unfortunately,
I'm
gonna
have
to
disappoint
people
with
this
answer
that
I
don't
know
the
numbers
off.
The
top
of
my
head,
like
we
have,
because
of
the
differences
in
the
environment
and
having
to
run
with
is
we
just
haven't,
had
an
apples
to
apples
test
where
we
ran
Castro
and
NCM
in
Prague
on
the
same
machine,
but
it
Kestrel
is
still
definitely
faster.
A
C
Because
there's
no
back
end
process
coming
up,
that's
looking
for
an
ephemeral
port
to
bind
to
it's,
just
whatever
binding
you
set
up
with,
is
and
when
the
the
way
that
works
is
when
you
create
a
bind
when
you
create
a
new
website
nice
and
create
a
binding
there's,
a
port
reservation
with
HT
pieces.
So
you
can
rest
assured.
No
one
is
stolen.
Your
port
and
you're
not
gonna.
Have
those
annoying
issues.
C
Awesome.
That
being
said,
I
want
to
say
it
like
we're
fully
aware
of
the
you
know,
the
port
exhaustion
and
like
the
port
conflict
issues
and
where
we're
really
trying
to
fix
it
and
we
hope
in
the
2-1
timeframe.
That's
not
the
reason
why
you
have
to
pick
in
prague
verses
out
of
prague.
You
know
we
should
have
addressed
all
those
issues
by
then.
C
A
Didn't
know
if
that
was
related
in
the
is
integration,
alright,
any
any
other
questions
folks.
This
is
exciting.
This
is
really
cool
I'm,
for
you
know
for
a
lot
of
reasons,
but
definitely
like
so
it's
easy
to
focus
on
the
purse
side,
but,
as
you
pointed
out
to
me,
the
ability
to
kind
of
bring
that
actually
did.
You
show
that
in
the
actually.
C
Okay,
so
this
is
for,
for
folks
are
curious.
This
is
how
it
actually
works.
So
this
is
a
flow
chart
that
I
have
of
what
happens
when
a
request
enters
the
is
worker
process
right.
So
when
you,
your
request,
comes
in
there's
a
call
to
get
application,
and
this
is
one
of
the
things
which
is
part
of
the
contract
between
the
Shem
and
the
request
handler
so
get
application
will
would
would
give
you
back
an
application
which
the
request
handle
would
specify
and
so
we're
gonna
look
at
the
part
of
the
flowchart.
C
C
A
C
C
C
C
I
think
the
eyes
integration
package
might
sorry,
so
I
obviously
am
blanking
out
for
a
second
but
I
think
yeah.
So
this
is
the
new
package
that
we've
introduced.
Ok,
so
the
reason
I
didn't
see
on
nuke.
It
is
in
the
preview
one
time
frame.
It
wasn't
actually
made
part
of
the
meta
package.
Yet
ok,
but
so
there's
this
new
package,
so
you
don't
have
to
explicitly
reference
it
because
it's
you
know,
part
meta
package.
C
C
Yep,
it
would
be
very
different.
That's
we
have
no
plans
to
do
it,
but
I
do
want
to
find
out
that
we've
actually
looked
into
the
feasibility
of
it
and
it's
I
know.
This
was
a
couple
of
folks
us
like
moonlighting,
this
not
really
in
any
official
capacity,
but
we
did
look
at
whether
it's
possible
to
do
it
with
nginx
unit.
It's
definitely
doable
I
wish
we
had
wish
I
could
do
it,
but
I
definitely
need
some
more
help,
but
there's
no
there's
no
official
Microsoft
plans
to
do
it
right
now.
Ok,.
A
C
It
never
hurts
to
reach
out.
You
know
if
someone
wants
to
by
all
means
reach
out
to
me.
I,
don't
know
in
what
capacity
we
can
help.
We
will
definitely
entertain
that
conversation
and
if
there
is
enough
community,
like
you,
know,
interest
around
it,
then
you
know
we
can
always
take
that
as
an
ask
and
see
what
we
can
do.
Awesome.
A
C
Till
the
end
yeah
so
far,
there
is
no
support
for
full
framework,
nor
is
it
flattened
at
the
moment.
So
if
you
want
to
run
asp.net
core
in
your
is
worker
process,
you
have
to
target
course
LR.
You
can't
target
full
framework
right
now,
got
it
okay
and
the
other
with
rather
significant
catches.
You
can
only
have
one
application
per
app
full
because
there
are
no
app
domains
in
the
core
cell
are
so
we
can't
load
multiple
versions
of
the
core
CLR,
so
you
have
to
stick
to
one
application
per
app
pool.
C
A
C
So,
ideally,
that's
how
you
should
be
running
like
mm-hmm
excuse
me,
that's
been
our
guidance
for
a
while.
Now,
like
you
get
better
isolation,
but
I
know,
especially
folks
who
Don
you
know
which
shared
hosters.
It's
like
you
paper
application,
so
there's
a
tendency
to
put
multiple
apps
in
a
single,
a
pool.
C
A
B
C
Work,
it
won't
work
today
because
the
the
global
changes
required
for
it
have
not
been
deployed
right.
It
will
it's
something
we
plan
to
do
along
with
our
release.
I
think
I,
don't
know
what
the
next
release
I
think
preview
to
xanax
release
mile.
So
I
I
don't
know
beyond
that,
but
whenever
we
do,
a
release
that
has
a
go
live
license
will
have
support
for
it
in
Azure
and
it
would
be
the
same
thing.
A
A
C
That's
an
a
point
that
I
glossed
over
so
and
I
was
talking
about
the
version
agility
and
the
ability
to
you
know
bring
your
own
request
handler
with
you.
It
also
the
another
unsaid
implication
of
that
is,
you
can
say,
start
consuming
Knightley's
or
start
consuming
releases
at
a
cadence.
You
don't
have
to
wait
for
us
to
globally
update
the
platform
special
measure.
B
A
C
A
A
B
C
B
C
A
Great
yeah
and
that's
part
of
the
series
that
we
we've
got
on
on
asp
net
core
2.1
preview,
one
so
that
that's
included
there
too
so,
and
I've
included
that
in
the
chat.
Also,
thank
you
awesome.
So
this
is
the
part
of
the
show
where
we
normally
do
a
dramatic
zoom
out
and
I'm,
not
sure
if
you're,
if
you're
prepared
to
handle
this
there's
a
the
remote
writing.