Thanks for clarifying that, that helps a lot :)
It might be an idea indeed to consider adding it to the spec if we
keep it in.
Server sided it shouldn't be -to hard- to parse the multipart and use
the same internal request & response structures, i'll go see what i
can do with that.
If you could find that javascript that be great.
-- Chris
On Jun 25, 2008, at 3:13 AM, John Panzer wrote:
Yeah, this was talked about on Friday but I guess Cassie didn't have
time to
mail the list before going on vacation.
It's possible to implement the spec (mime/multipart) in Javascript,
in fact
we did it a few months back as a sanity check, I'll need to dig up
the code
to send around.
The discussion so far has been that it's faster to just implement the
JSON-only batch format for now. The spec doesn't disallow this as the
/batch-proxy URL can accept any MIME type you care to throw at it (and
define), if we decide to standardize the JSON one we should probably
write
up some spec text though :). application/json batch can co-exist with
mime/multipart easily enough if necessary.
John Panzer (http://abstractioneer.org)
On Tue, Jun 24, 2008 at 6:04 PM, Kevin Brown <[EMAIL PROTECTED]> wrote:
On Tue, Jun 24, 2008 at 5:54 PM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
Did you forget the apache meme? If it's not in my mailbox, it
doesn't
exist
! :-)
Yeah, there's not really anything to send around though -- we
talked about
it, but nobody really had a good idea about what to do. I assume that
Cassie
was taking care of it since she's been working in that area.
Might be nice to keep us who are not privy to the google meetings
involved
in it? (both spec and shindig wise), else we'll end up having people
spinning their wheels for nothing, and no one likes to loose time,
even
just
some heads up would be useful for the people involved. (we went by
cassie's
words "as soon as the php guys implement batching you can flip the
switch",
so i had no insight in nor hints to these discussions)
Well, there weren't actually any proposals for what to do, so there
wasn't
anything to share. If someone has a good idea of how to do it and
wants to
write it, by all means go for it. If you can make it work for PHP
I'm sure
it can be adapted for Java (there's certainly no reason why the PHP
code
has
to follow the lead of what's done in the Java base, after all).
What's the problem, impossible to make such a request from
javascript
(something i could imagine)? In that case i guess at least we can
keep
the
work we did so far on the php side.
I don't know; David and Cassie had different opinions on the
matter, so
they
talked to try to sort it out. I don't think they came to any
conclusion on
the matter, so hopefully someone with better ideas will :).
-- Chris
On Jun 25, 2008, at 2:47 AM, Kevin Brown wrote:
Several of us have been discussing this problem over at Google,
but I
don't
know that there was a clear conclusion
