You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Chris Chabot <ch...@google.com> on 2009/05/05 14:29:47 UTC
Re: [OpenSocial] Shindig doesn't render todo test application
Hey Arlo,
First of, the best mailing list for shindig related questions is
shindig-dev@incubator.apache.org (cc'd), see
http://incubator.apache.org/shindig/community/getting-help.html for
instructions on how to sign up for that.
Once i force-refreshed (shift + clicking the refresh button in firefox),
it's showing the gadget rendered correctly for me, however on the first try
before that I did see the incomplete one and noticed some curl errors in the
proxied javascript files of the todo gadget.
Since it does work, I'm guessing that maybe the curl fetching time out might
be to low, and some resources fail fetching because of that? There's a
configuration key in shindig/php/container.php where you could increase
that:
'curl_connection_timeout' => '10',
Setting that to 30 seconds should fix the problem, if that was indeed the
issue.
So it looks like in theory your installation seems to be working as it
should. If you want to have a 'real' test case for kicking the tires, and as
an example of how to integrate your own data back-end with shindig, I'd
advice you to check out partuza, a example social network site I wrote for
just those 2 reasons.
The code and instructions are at: http://code.google.com/p/partuza
and a live version so you can see what to expect is located at:
http://www.partuza.nl
Good luck and if you run into any issues, please feel free to mail us on the
shindig-dev list!
-- Chris
On Tue, May 5, 2009 at 2:14 PM, arlo <iv...@gmail.com> wrote:
>
> Hy everyone,
>
> I just started to study OpenSocial and about to get my Shindig server
> running. But I ran into my first big problem. It's the todo test
> application which doesn't want to render itself as it should.
>
> Here is the link:
>
> http://shindig.linker.hr/gadgets/ifr?url=http://www.labpixies.com/campaigns/todo/todo.xml
>
> There is the Shindig server (v0.8) trying to take the todo application
> and render it in browser. All I get is visually incompletely rendered
> application with no features what so ever.
>
> So I suspect for the Shindig server not doing the job right.
>
> Can anyone help?
> Thanks very much.
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "Implementing OpenSocial Containers" group.
> To post to this group, send email to opensocial-container@googlegroups.com
> To unsubscribe from this group, send email to
> opensocial-container+unsubscribe@googlegroups.com<op...@googlegroups.com>
> For more options, visit this group at
> http://groups.google.com/group/opensocial-container?hl=en
> -~----------~----~----~----~------~----~------~--~---
>
>
RE: [OpenSocial] Re: Shindig doesn't render todo test application
Posted by Ivan Arar <iv...@gmail.com>.
Hi,
Looks like this thread is not ver after all J
I discovered why opensocial applications won't work/render properly within my project locally and are working/rendering using remote server.
The thing is I use 0.8 version on remote server and 0.9 locally. When I changed from 0.9 to 0.8 locally they started to render just fine.
I suppose 0.9 is better but that means nothing to me.
From: opensocial-container@googlegroups.com [mailto:opensocial-container@googlegroups.com] On Behalf Of Chris Chabot
Sent: 5. svibanj 2009 14:30
To: opensocial-container@googlegroups.com; shindig-dev@incubator.apache.org
Subject: [OpenSocial] Re: Shindig doesn't render todo test application
Hey Arlo,
First of, the best mailing list for shindig related questions is shindig-dev@incubator.apache.org (cc'd), see http://incubator.apache.org/shindig/community/getting-help.html for instructions on how to sign up for that.
Once i force-refreshed (shift + clicking the refresh button in firefox), it's showing the gadget rendered correctly for me, however on the first try before that I did see the incomplete one and noticed some curl errors in the proxied javascript files of the todo gadget.
Since it does work, I'm guessing that maybe the curl fetching time out might be to low, and some resources fail fetching because of that? There's a configuration key in shindig/php/container.php where you could increase that:
'curl_connection_timeout' => '10',
Setting that to 30 seconds should fix the problem, if that was indeed the issue.
So it looks like in theory your installation seems to be working as it should. If you want to have a 'real' test case for kicking the tires, and as an example of how to integrate your own data back-end with shindig, I'd advice you to check out partuza, a example social network site I wrote for just those 2 reasons.
The code and instructions are at: http://code.google.com/p/partuza
and a live version so you can see what to expect is located at: http://www.partuza.nl
Good luck and if you run into any issues, please feel free to mail us on the shindig-dev list!
-- Chris
On Tue, May 5, 2009 at 2:14 PM, arlo <iv...@gmail.com> wrote:
Hy everyone,
I just started to study OpenSocial and about to get my Shindig server
running. But I ran into my first big problem. It's the todo test
application which doesn't want to render itself as it should.
Here is the link:
http://shindig.linker.hr/gadgets/ifr?url=http://www.labpixies.com/campaigns/todo/todo.xml
There is the Shindig server (v0.8) trying to take the todo application
and render it in browser. All I get is visually incompletely rendered
application with no features what so ever.
So I suspect for the Shindig server not doing the job right.
Can anyone help?
Thanks very much.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" group.
To post to this group, send email to opensocial-container@googlegroups.com
To unsubscribe from this group, send email to opensocial-container+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en
-~----------~----~----~----~------~----~------~--~---
Re: [OpenSocial] Re: Shindig doesn't render todo test application
Posted by Chris Chabot <ch...@google.com>.
On Tue, May 5, 2009 at 3:05 PM, Ivan Arar <iv...@gmail.com> wrote:
> Hey,
>
> Sorry for posting to wrong group. Hope I hit the right one now.
>
No worries, having an opensocial-containers group does tend to lead people
down that path more often; But as far as shindig developers and support
goes, you'll find a lot more of it here :)
Looks like forced-refresh worked! Although I find this very strange because
> I refreshed the page numerous time before.
>
Shindig tries to cache, and cache and cache some more ... when your running
in full production and getting tens to thousands of hits a second, well it
goes a long way to helping the gadget's servers to survive the traffic; Also
the web browser is told to cache things as much and long as possible, so
sometimes if there were timeouts or errors in the curl module, it can cache
an invalid document.
force-refresh in the web browser has 2 functions, first of all it forces it
to re-download the image even if the max-age cache control told it not too
for that duration, and it also sends a pragma: no-cache to the server that
php-shindig honors (it will re-fetch the document even if it has a cached
version of that file), so it's a good way to double check.
While developing these things can sometimes occur, the easiest way to make
sure you start out with a clean situation is by cleaning out the cache
directory (the default config is set to use file based caching, which it
stores in the /tmp/shindig directory), so doing a rm -rf /tmp/shindig gives
you a completely clean start again.. combine that with a force-refresh in
the web browser (to make sure it won't use it's browsers cache), and you
have a complete reset situation again.
> Anyway, my remote Shindig server is working now but localy neither
> force-refresh nor 30 sec curl timeout worked.
>
Possibly your behind a proxy server? If so there's a config for that too in
config/container.php:
// If your development server is behind a proxy, enter the proxy details
here in 'proxy.host.com:port' format.
'proxy' => '',
> Yes, I already took Partuza into my hands and majority of my work for now
> is based on it. Thanks for wroting that J
>
Glad to hear it's useful :)
Good luck and let us know how things go!
-- Chris
RE: [OpenSocial] Re: Shindig doesn't render todo test application
Posted by Ivan Arar <iv...@gmail.com>.
Hey,
Sorry for posting to wrong group. Hope I hit the right one now.
Looks like forced-refresh worked! Although I find this very strange because I refreshed the page numerous time before.
Anyway, my remote Shindig server is working now but localy neither force-refresh nor 30 sec curl timeout worked.
So for now I'll continue my development using that remote server which I'm in control with.
Yes, I already took Partuza into my hands and majority of my work for now is based on it. Thanks for wroting that J
From: opensocial-container@googlegroups.com [mailto:opensocial-container@googlegroups.com] On Behalf Of Chris Chabot
Sent: 5. svibanj 2009 14:30
To: opensocial-container@googlegroups.com; shindig-dev@incubator.apache.org
Subject: [OpenSocial] Re: Shindig doesn't render todo test application
Hey Arlo,
First of, the best mailing list for shindig related questions is shindig-dev@incubator.apache.org (cc'd), see http://incubator.apache.org/shindig/community/getting-help.html for instructions on how to sign up for that.
Once i force-refreshed (shift + clicking the refresh button in firefox), it's showing the gadget rendered correctly for me, however on the first try before that I did see the incomplete one and noticed some curl errors in the proxied javascript files of the todo gadget.
Since it does work, I'm guessing that maybe the curl fetching time out might be to low, and some resources fail fetching because of that? There's a configuration key in shindig/php/container.php where you could increase that:
'curl_connection_timeout' => '10',
Setting that to 30 seconds should fix the problem, if that was indeed the issue.
So it looks like in theory your installation seems to be working as it should. If you want to have a 'real' test case for kicking the tires, and as an example of how to integrate your own data back-end with shindig, I'd advice you to check out partuza, a example social network site I wrote for just those 2 reasons.
The code and instructions are at: http://code.google.com/p/partuza
and a live version so you can see what to expect is located at: http://www.partuza.nl
Good luck and if you run into any issues, please feel free to mail us on the shindig-dev list!
-- Chris
On Tue, May 5, 2009 at 2:14 PM, arlo <iv...@gmail.com> wrote:
Hy everyone,
I just started to study OpenSocial and about to get my Shindig server
running. But I ran into my first big problem. It's the todo test
application which doesn't want to render itself as it should.
Here is the link:
http://shindig.linker.hr/gadgets/ifr?url=http://www.labpixies.com/campaigns/todo/todo.xml
There is the Shindig server (v0.8) trying to take the todo application
and render it in browser. All I get is visually incompletely rendered
application with no features what so ever.
So I suspect for the Shindig server not doing the job right.
Can anyone help?
Thanks very much.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" group.
To post to this group, send email to opensocial-container@googlegroups.com
To unsubscribe from this group, send email to opensocial-container+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/opensocial-container?hl=en
-~----------~----~----~----~------~----~------~--~---