We encountered interesting issues with Firefox and caching bugs. The
main outer page would properly refresh, but the iframe would not take
the new URL. It's a known FF bug. Our workaround is to code the iframe
like:

<iframe id="x1">
-- place the calls to setAuthToken here --
<script>document.getElementById("x1").src="<the iframe src>";</script>

This also helped old IE's use the VB method for rpc, we were using an
old version of rpc, don't know if the newer one would have the same
issue.

Jon

-----Original Message-----
From: Fayland Lam [mailto:fayl...@gmail.com] 
Sent: Wednesday, November 11, 2009 12:01 AM
To: shindig-dev@incubator.apache.org
Subject: two questions after deploy

first of all, thumb up for shindig. we just released our opensocial
application some days ago (beckend as shindig) if anyone is interested,
this is the URL: http://app.zorpia.com/poker

question 1.
reload issue. well, see if we open a firefox tab with the URL above. 
then you close the firefox. we wait some minutes, then open the firefox.
the firefox loads the previous tab (with old st= token). then opensocial
shindig returns 500 errors because 'Security token expired'.

I know that's right. but how can we avoid it? with no-cache header? it
seems not working? any suggestions?

question 2:
http://org112.zpcdn.cn/0/5577/35697007.d077c9.jpg
it works in IE7,8 and Firefox. but with Mac OS, there is the debug
error. any thoughts?

Thanks.

--
Fayland Lam // http://www.fayland.org/

Reply via email to