| From | Sent On | Attachments |
|---|---|---|
| James Snell | Jan 26, 2012 1:35 pm | |
| James Snell | Jan 26, 2012 1:35 pm | |
| Henry Saputra | Jan 26, 2012 8:34 pm | |
| Henry Saputra | Jan 26, 2012 8:34 pm | |
| Mark W. | Jan 30, 2012 5:20 am | |
| James Snell | Jan 30, 2012 8:08 am | |
| James Snell | Jan 30, 2012 8:08 am | |
| Mark W. | Jan 30, 2012 11:05 am | |
| Matthew Marum | Feb 2, 2012 1:22 pm | |
| Li Xu | Feb 3, 2012 8:05 am | |
| Li Xu | Feb 3, 2012 8:05 am | |
| Mark W. | Feb 3, 2012 8:18 am | |
| Matthew Marum | Feb 3, 2012 9:09 am | |
| Matthew Marum | Feb 3, 2012 9:09 am | |
| James Snell | Feb 3, 2012 2:15 pm | |
| James Snell | Feb 3, 2012 2:16 pm | |
| Bastian Hofmann | Feb 5, 2012 3:25 am | |
| Bastian Hofmann | Feb 5, 2012 3:25 am | |
| Mark W. | Feb 6, 2012 3:39 pm | |
| James Snell | Feb 6, 2012 3:43 pm | |
| James Snell | Feb 6, 2012 3:43 pm | |
| Laurent-Walter Goix | Feb 7, 2012 2:26 pm | |
| James Snell | Feb 7, 2012 4:25 pm | |
| James Snell | Feb 7, 2012 4:25 pm | |
| Henry Saputra | Feb 7, 2012 4:44 pm | |
| Henry Saputra | Feb 7, 2012 4:44 pm | |
| Mark W. | Feb 7, 2012 5:50 pm | |
| James Snell | Feb 7, 2012 7:47 pm | |
| James Snell | Feb 7, 2012 7:47 pm | |
| Henry Saputra | Feb 7, 2012 8:13 pm | |
| Henry Saputra | Feb 7, 2012 8:13 pm | |
| James Snell | Feb 7, 2012 8:21 pm | |
| James Snell | Feb 7, 2012 8:21 pm | |
| Henry Saputra | Feb 7, 2012 8:37 pm | |
| Henry Saputra | Feb 7, 2012 8:38 pm | |
| James Snell | Feb 7, 2012 8:48 pm | |
| James Snell | Feb 7, 2012 8:48 pm | |
| Craig McClanahan | Feb 7, 2012 9:22 pm | |
| Craig McClanahan | Feb 7, 2012 9:22 pm | |
| James Snell | Feb 7, 2012 10:26 pm | |
| James Snell | Feb 7, 2012 10:26 pm | |
| Mark W. | Feb 8, 2012 9:05 am | |
| James Snell | Feb 8, 2012 9:22 am | |
| James Snell | Feb 8, 2012 9:22 am | |
| Mark W. | Feb 9, 2012 8:33 am |
| Subject: | Re: [osgs] Re: Batch Support in RPC Protocol: A quick survey | |
|---|---|---|
| From: | James Snell (jasn...@gmail.com) | |
| Date: | Feb 3, 2012 2:15:59 pm | |
| List: | com.googlegroups.opensocial-and-gadgets-spec | |
Hmm.. just so I fully understand.. how does this batching up requests to external sites thing work? One request to my server results in n-requests to n-separate other servers? If so, how does the response data get composed and returned to my browser? Is there a requirement that all the external requests must return like-structured/formatted data? Does it only work for GETs? How are individual error conditions handled? How is authentication handled? None of this is specified within the Core API specification that defines the basic batching mechanism so I'm pretty much just left to guessing how it it's supposed to maybe possibly work.
On Fri, Feb 3, 2012 at 9:10 AM, Matthew Marum <mgma...@gmail.com> wrote:
I agree that the REST model I proposed is a little awkward if we translate it directly to the JavaScript API, maybe it should work differently there. But I think it's a good direction to take the REST APIs to make them more robust.
That is a good point about external sites. Batch requests are a convenient way to line up a bunch of HTTP requests that need to be proxied.
Matt
On Fri, Feb 3, 2012 at 11:18 AM, Mark W. <weit...@gmail.com> wrote:
Sure.... So while we might be able to modify the rest api to support this, how would this get exposed via JavaScript? Did we just hose up the programming model by forcing a bunch of parameters on the people service? Not sure....
Also remember you can batch up calls to external sites, not just those to the container.
I guess what I'm lacking is the real context behind the question. What is the reason to get rid of batch? Is it b/c we want just REST? What am I missing?
-- You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group. To view this discussion on the web visit https://groups.google.com/d/msg/opensocial-and-gadgets-spec/-/rQFJfqP99S0J.
To post to this group, send email to open...@googlegroups.com. To unsubscribe from this group, send email to opensocial-and-gadgets-spec+unsu...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
-- You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group. To post to this group, send email to open...@googlegroups.com. To unsubscribe from this group, send email to opensocial-and-gadgets-spec+unsu...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
--
You received this message because you are subscribed to the Google Groups
"OpenSocial and Gadgets Specification Discussion" group.
To post to this group, send email to
open...@googlegroups.com.
To unsubscribe from this group, send email to
opensocial-and-gadgets-spec+unsu...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.





