<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: RFacebook Updates!</title>
	<link>http://www.livelearncode.com/archives/22</link>
	<description>my reflections on stuff</description>
	<pubDate>Sun, 19 May 2013 08:15:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.3</generator>

	<item>
		<title>by: Raghu</title>
		<link>http://www.livelearncode.com/archives/22#comment-933</link>
		<pubDate>Wed, 22 Aug 2007 22:10:34 +0000</pubDate>
		<guid>http://www.livelearncode.com/archives/22#comment-933</guid>
					<description>Thanks for the clarification. Yes, I agree caching and expiring caches can get pretty complicated fast ... what you have is good enough for me now.</description>
		<content:encoded><![CDATA[<p>Thanks for the clarification. Yes, I agree caching and expiring caches can get pretty complicated fast &#8230; what you have is good enough for me now.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Matt</title>
		<link>http://www.livelearncode.com/archives/22#comment-926</link>
		<pubDate>Tue, 21 Aug 2007 18:52:06 +0000</pubDate>
		<guid>http://www.livelearncode.com/archives/22#comment-926</guid>
					<description>The cache lasts for as long as the fbsession is in memory.  It is a very simple in-memory cache that persists with the FacebookSession object.

This actually varies depending on the way that you use the plugin.  If you are making a Canvas app, you have a new session on every request.  If you are making an iframe or external app, then that session is persisted in session[:rfacebook_session], and you can nil that out when it is not needed anymore.

In the future, I would like to make the caching smarter, but I think that a real caching solution should be implemented on an app-by-app basis.  There really isn't a magic bullet for such things.</description>
		<content:encoded><![CDATA[<p>The cache lasts for as long as the fbsession is in memory.  It is a very simple in-memory cache that persists with the FacebookSession object.</p>
<p>This actually varies depending on the way that you use the plugin.  If you are making a Canvas app, you have a new session on every request.  If you are making an iframe or external app, then that session is persisted in session[:rfacebook_session], and you can nil that out when it is not needed anymore.</p>
<p>In the future, I would like to make the caching smarter, but I think that a real caching solution should be implemented on an app-by-app basis.  There really isn&#8217;t a magic bullet for such things.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Raghu Srinivasan</title>
		<link>http://www.livelearncode.com/archives/22#comment-925</link>
		<pubDate>Tue, 21 Aug 2007 18:45:55 +0000</pubDate>
		<guid>http://www.livelearncode.com/archives/22#comment-925</guid>
					<description>Thanks for RFacebook. I've just started to play with it. I have a question on caching - how long does the cache last? Is there a way to expire it explicity or set a TTL?

Raghu Srinivasan</description>
		<content:encoded><![CDATA[<p>Thanks for RFacebook. I&#8217;ve just started to play with it. I have a question on caching - how long does the cache last? Is there a way to expire it explicity or set a TTL?</p>
<p>Raghu Srinivasan
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
