From 6f3343a6300c20fd2b5f7614ab015593d2731636 Mon Sep 17 00:00:00 2001 From: "Michael J. Rubinsky" Date: Fri, 2 Jul 2010 20:13:10 -0400 Subject: [PATCH] caching the twitter api requests cause some strange side effects, disable it for now. Caching the stream can result in newer tweets, that may have appeared in the stream due to the ajax updates, from NOT being shown when the entire page is reloaded. --- framework/Core/lib/Horde/Core/Binder/Twitter.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/framework/Core/lib/Horde/Core/Binder/Twitter.php b/framework/Core/lib/Horde/Core/Binder/Twitter.php index ce0676a8f..c032111e0 100644 --- a/framework/Core/lib/Horde/Core/Binder/Twitter.php +++ b/framework/Core/lib/Horde/Core/Binder/Twitter.php @@ -33,7 +33,7 @@ class Horde_Core_Binder_Twitter implements Horde_Injector_Binder $request = new Horde_Service_Twitter_Request_Oauth(); $twitter = new Horde_Service_Twitter($auth, $request); - $twitter->setCache($injector->getInstance('Horde_Cache')); + //$twitter->setCache($injector->getInstance('Horde_Cache')); $twitter->setLogger($injector->getInstance('Horde_Log_Logger')); $twitter->setHttpClient($GLOBALS['injector']->getInstance('Horde_Http_Client')); -- 2.11.0