You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by WangZhongyu <zz...@gmail.com> on 2009/03/06 02:51:21 UTC
merge multiple gadgets' makeRequest requests into one?
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
Re: merge multiple gadgets' makeRequest requests into one?
Posted by Adam Winer <aw...@gmail.com>.
Why not use the <Preload> element to load all of those resources up
front, without any round-trips from the client?
On Thu, Mar 5, 2009 at 10:28 PM, WangZhongyu <zz...@gmail.com> wrote:
> thx Dan Peterson. In my scenario, I want to refactor my legacy application
> into gadgets.
> Therefore, all the backend restful services are all in the same site. And In
> the creation
> peroid of the gadgets, the makerequest method is executed too much.
>
> I want to merge across serveral gadegets of which backend restful services
> are all in
> the same site.
>
> Is it possible to reduce the http requests for the situation that muliple
> gadgets having
> different domains backend restful services ?
>
> 2009/3/6 Dan Peterson <dp...@google.com>
>
>> 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 <gu...@gmail.com>
>> 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 <lr...@google.com> 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 <zz...@gmail.com> 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 <zz...@gmail.com>
>> > > >
>> > > > > 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
>> > > > >
>> > > >
>> > >
>> >
>>
>
Re: merge multiple gadgets' makeRequest requests into one?
Posted by WangZhongyu <zz...@gmail.com>.
thx Dan Peterson. In my scenario, I want to refactor my legacy application
into gadgets.
Therefore, all the backend restful services are all in the same site. And In
the creation
peroid of the gadgets, the makerequest method is executed too much.
I want to merge across serveral gadegets of which backend restful services
are all in
the same site.
Is it possible to reduce the http requests for the situation that muliple
gadgets having
different domains backend restful services ?
2009/3/6 Dan Peterson <dp...@google.com>
> 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 <gu...@gmail.com>
> 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 <lr...@google.com> 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 <zz...@gmail.com> 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 <zz...@gmail.com>
> > > >
> > > > > 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
> > > > >
> > > >
> > >
> >
>
Re: merge multiple gadgets' makeRequest requests into one?
Posted by Dan Peterson <dp...@google.com>.
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 <gu...@gmail.com> 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 <lr...@google.com> 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 <zz...@gmail.com> 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 <zz...@gmail.com>
> > >
> > > > 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
> > > >
> > >
> >
>
Re: merge multiple gadgets' makeRequest requests into one?
Posted by yingshou guo <gu...@gmail.com>.
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 <lr...@google.com> 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 <zz...@gmail.com> 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 <zz...@gmail.com>
> >
> > > 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
> > >
> >
>
Re: merge multiple gadgets' makeRequest requests into one?
Posted by Louis Ryan <lr...@google.com>.
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 <zz...@gmail.com> 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 <zz...@gmail.com>
>
> > 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
> >
>
Re: merge multiple gadgets' makeRequest requests into one?
Posted by WangZhongyu <zz...@gmail.com>.
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 <zz...@gmail.com>
> 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
>