You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Ropu <ro...@gmail.com> on 2008/09/18 21:32:45 UTC
Preloads that return != HTTP 200
Hi guys
how should we handle preloads that when calling it from server side to
inline it in the JS return an HTTP status != of 200?
we should ignore that preload an leave the JS to the actual makeRequest()?
or inline the HTTP with the error?
ropu
--
.-. --- .--. ..-
R o p u
Re: Preloads that return != HTTP 200
Posted by Louis Ryan <lr...@google.com>.
I think its OK for the gadget developer to retry the request as they see
fit. The error might actually be useful information that they can take
advantage of.
On Thu, Sep 18, 2008 at 12:40 PM, Ropu <ro...@gmail.com> wrote:
> Yes, thats what im doing.
>
> but sometimes happen that the error was because a time out, since those
> throttles for server side are sometimes small. so i thought that, as we do
> in cache, that we ignore HTTP != 200, maybe in the preload we do it too, is
> like giving an other chance to actually get a HTTP 200 in the
> gadgets/makeRequest.
>
>
>
>
> On Thu, Sep 18, 2008 at 4:36 PM, Kevin Brown <et...@google.com> wrote:
>
> > On Thu, Sep 18, 2008 at 9:32 PM, Ropu <ro...@gmail.com> wrote:
> >
> > > Hi guys
> > >
> > > how should we handle preloads that when calling it from server side to
> > > inline it in the JS return an HTTP status != of 200?
> >
> >
> > The same way that makeRequest handles it -- by storing rc & errors in the
> > response object.
> >
> >
> > >
> > >
> > > we should ignore that preload an leave the JS to the actual
> > makeRequest()?
> > >
> > > or inline the HTTP with the error?
> > >
> > > ropu
> > >
> > > --
> > > .-. --- .--. ..-
> > > R o p u
> > >
> >
>
>
>
> --
> .-. --- .--. ..-
> R o p u
>
Re: Preloads that return != HTTP 200
Posted by Ropu <ro...@gmail.com>.
Yes, thats what im doing.
but sometimes happen that the error was because a time out, since those
throttles for server side are sometimes small. so i thought that, as we do
in cache, that we ignore HTTP != 200, maybe in the preload we do it too, is
like giving an other chance to actually get a HTTP 200 in the
gadgets/makeRequest.
On Thu, Sep 18, 2008 at 4:36 PM, Kevin Brown <et...@google.com> wrote:
> On Thu, Sep 18, 2008 at 9:32 PM, Ropu <ro...@gmail.com> wrote:
>
> > Hi guys
> >
> > how should we handle preloads that when calling it from server side to
> > inline it in the JS return an HTTP status != of 200?
>
>
> The same way that makeRequest handles it -- by storing rc & errors in the
> response object.
>
>
> >
> >
> > we should ignore that preload an leave the JS to the actual
> makeRequest()?
> >
> > or inline the HTTP with the error?
> >
> > ropu
> >
> > --
> > .-. --- .--. ..-
> > R o p u
> >
>
--
.-. --- .--. ..-
R o p u
Re: Preloads that return != HTTP 200
Posted by Kevin Brown <et...@google.com>.
On Thu, Sep 18, 2008 at 9:32 PM, Ropu <ro...@gmail.com> wrote:
> Hi guys
>
> how should we handle preloads that when calling it from server side to
> inline it in the JS return an HTTP status != of 200?
The same way that makeRequest handles it -- by storing rc & errors in the
response object.
>
>
> we should ignore that preload an leave the JS to the actual makeRequest()?
>
> or inline the HTTP with the error?
>
> ropu
>
> --
> .-. --- .--. ..-
> R o p u
>