To be clear, do you mean merging across several gadgets or merging several makeRequests from a single gadget? -Dan
On Fri, Mar 6, 2009 at 2:40 PM, yingshou guo <[email protected]> wrote: > Louis, > Would you like to share your codes/ideas about batching makeRequest from > different gadgets? Thanks in advance. > > > > > On Fri, Mar 6, 2009 at 10:05 AM, Louis Ryan <[email protected]> wrote: > > > I have code that reworks makeRequest to use the JSON-RPC protocol which > > would allow for batching HTTP requests. I'd like to see this standardized > > as > > part of the osapi effort. > > > > On Thu, Mar 5, 2009 at 5:59 PM, WangZhongyu <[email protected]> wrote: > > > > > And this problem highlights just in the gadgets creation period, > > afterwards > > > end user can't click muliple gadgets in one time, it won't be a problem > > > that > > > time. > > > > > > 2009/3/6 WangZhongyu <[email protected]> > > > > > > > I'm a newbie in shindig. > > > > In my thoughts, opensocial.* api's "newDataRequest" can merge > mulitple > > > > requests into one byrecursively execute"req.add(...)". > > > > > > > > But in gadgets.*, when a container consists of too many gadgets, it > may > > > be > > > > a disaster for gadgets > > > > to create and makerequest. Too many http requests is a waste of > > resource > > > > and not a good user > > > > experience for the end user. > > > > > > > > Are there any stable solutions to solve this problem, or maybe it's > > just > > > > hiding in somewhere, and > > > > I miss it. > > > > > > > > Thx for any advice > > > > > > > > > >
