►
From YouTube: Magento Async Import #14 - All Your Base64 Are Belong To Us (Community Meeting Mar 13 2019)
Description
In this episode, Alex judges Igor for being on a different meeting. Hitarth invades with a lot of great work completed on refactoring and proposal regarding partial upload of base64 encoded files.
A
Yeah,
in
addition,
I
also
merged
this,
a
reputable,
no,
not
repeatable,
call
to
merge
this,
the
current
yeah.
It
was
status
endpoints
and
we
go
directly
than
you
want
for
you
couldn't
sometimes
it's
slow,
very
slow,
yeah
yeah
our
repeater
will
call
end
point:
I
had
no
time
to
check
it
yet
I'm
on
it.
A
A
B
A
B
A
B
B
This
was
the
issue.
Initially,
there
was
a
couple
of.
There
are
mainly
three
pool
or
three
pool
requests
for
three
different
processors,
and
we
were
facing
the
same
issue.
You
know
like
I,
have
injected
source
type
to
each
of
these
processors,
and
then
I
got
I
saw
the
issue
that
you
know
like
it's
keep.
It
is
duplicating
to
each
and
every
processors
and
injecting
into
the
D
I
got
X,
and,
and
so
there
was
a
issue
to
suggest,
to
create
another
post
pool
and
injecting
persistent
persistent
processors
to
process
those
requests.
B
Basically,
I
have
related
all
the
quotes.
All
the
processor
calls
64,
which
was
created
by
me
itself
and
then
local
processors
and
external
external
sources,
external
file,
processor,
I,
have
related
every
processors
and
injected
persistent
processor
pool
and
and
I
write
it
down
the
I.
Would
he
find
the.
B
So
basically,
I
have
I
have
created
the
sauce
pool
and
I
have
injected
the
toast
type,
which
is
a
virtual
type
of
the
physical
source
type
file,
and
that
is
how
I've
injected,
probably,
if
later
on,
probably
we
should.
We
need
to
inject
another
XML
processor,
all
XML
file
type
or
something
so
that
we
can
inject
directly
with
the
toast
type
in
their
name
to
be
defined
and
that
were
to
attempt
it
needs
to
be
injected
into
the
sauce
will
type
in
the
sauce
pool.
B
So
initially
idea
was
to
create
the
abstract
processes
and
extending
to
all
the
other
processors,
but
just
I
just
got
an
update
that
you
know
like
we
are
not
using
the
inheritance
and
we
should
directly
inject
the
persistent
processes
into
different
different
processors,
so
I'm
I'm,
taking
one
example
of
a
base64
encode
data,
processor
and
I
have
done
the
same
thing
in
all
the
three
different
processors.
So
initially,
when
I
go
to
the
content,
I'm
setting
up
I
am
processing
the
content
in
the
base64.
I
am
converting
in
a
sixth
event
to
normal
content.
B
External
files,
I
am
reading
the
content
and
I
am
reading.
The
content
from
external
file
and
putting
into
the
source
and
the
same
where
in
the
local
files
I,
am
reading
the
content.
Basically,
I
am
reading
the
content
and
ascending
into
the
source
and
then
then,
later
on,
I
call
the
position
of
loaders
processed
upload
to
process
those
source
and
responses.
B
So
within
it,
I
am
having
grated
the
sauce
pool
tab
and
be
the
source
code.
I
am
defining
the
I
am
if
I'm
getting
the
source
a
source
type
based
on
the
request
that
I
am
getting
and
with
this
source
type
I'm
I'm,
saving
the
content.
I
am
saving
the
source
so
with
the
import
type
those
file
tab.
This
is
the
chill
file
where
I
returned
everything
generating
the
file.
Reading
the
content,
saving
the
data
processing,
the
source,
saving
the
source
and
eating
the
source
again.
B
A
B
So
I'm
working
on
the
partial
base64
import
I
was
I,
was
I,
was
thinking
of
implementing
those,
but
I
just
need
to
make
sure
that
you
know
like
we
were
on
the
same
page
and
what
you
guys
feel
about
processing
the
partial
request.
So
I
just
had
a
hard
couple
of
I
just
have
a
couple
of
questions
before
I
start
implementing
it
I'll
just
write
it
down
some
steps
to
be
implemented
but
haven't
been
implemented.
So
I
was
just
defining
the
architecture
how
to
implement
it
and
that
have
a
couple
of
questions
can
I
shoot.
B
B
C
C
C
B
A
C
C
So,
for
example,
like
we
have
data
URLs
that
may
encode
any
data
any
image
and
allow
it
to
embed
in
HTML
or
CSS,
so
it
contains
like
data
type
or
encoding
and
so
on,
and
it's
like
divided
by
columns
and
then
actually
base64
encoded
content
of
the
image.
So
we
mean
is
some
similar
approach
to
encode
the
see
information
import
date
like
like
some,
you
IDs.
It
will
in
identify
their
whole
files
like
split
it
into
several
chunks
like
in
colon
and
so
on.
A
A
C
It's
it
should
be
pretty
really
fuse
extension
attributes
for
entities
that
declared
in
the
same
module.
So
it's
extension
which
should
be
used
to
try
like
if
you
want
to
extend
some
entities.
That
is
declares
and
not
honored
by
my
ass,
but
provided
by
some
other
modules,
and
you
would
just
you
had
something
to
this
entity.
A
Basically,
if
you
like,
giving
a
possibility
to
developers
to
find
their
own
processors
for
blow
the
files
well,
this
can
be
also
like
one
step
like
separate
processor
notes
related
to
the
usual
base64
encoded
data.
But
like
all
one-
and
in
this
case
there
is
a
sense
to
move
this
like
an
extension
attribute,
because
it's
like
standalone
importer,
but
I
also
agree
that
if
you're
doing
it
like
a
part
of
the
system
itself,
extension
tube
is
not
a
very
good
way
here.
To
use.
C
B
B
A
A
So
I
said
yeah
I
would
ask
if
there
is
a
ticket
which
has
a
label
contribution
day,
and
please
don't
take
it
for
now,
because
I
won't
like
distribute
it
to
the
guys,
because
I
talked
to
graff
care
guys
and
the
challenges
they
making
a
ticket
for
Constitution
Day
and
they
directly
taken
by
somebody
so
I
would
better
to
delete
the
labels
after
I'll
back
toward
Monday
good.
Any
other
questions
for
you
guys.
B
A
Yeah
I
will
make
some
tasks
for
the
testing
and
I
will
present
it
on
contribution
day
because
usually
I'm
not
too
complex
and
they're
quite
nice
for
contribution
day
when
you
can
make
during
the
day
one
or
two
tasks,
so
yeah
I
will
do
them
and
I
will
also
label
them
and
I
will
remove
label
on
Sunday
or
Monday,
so
the
tickets
that
will
be
not
be
taken
by
somebody
I
will
remove
them.
I
mean
I
will
remove
the
labels,
and
then
you
can
take
it.
If
you
want
you.