yazgoo edited this page Sep 14, 2010 · 4 revisions

Developer view

Facebook graph api is a neat idea, but as these line are written, it still suffers from query latencies,
making its direct usage for webpages difficult. Some pages from this project with many queries took over 10 seconds to load!
Thats why a cache was created. The cache stores http requests results and identifies them by their url.
The facebook graph api php sdk in this project is a modified version using a proxy curl query method,
which may save the http result to cache or load it from it depending on conditions.

Cache clearing

In the current version, the cache can only be deleted. It can only be loaded by performing the end user page loading.
This mean that one specific request to a page between two cache clearing will be long.

Cache key

The cache can be deleted manually, by passing to the application a configuration specified get variable (main/cache/clear_key).
For example, if the clear key is set to my_clear_key and the application root is http://my.band.rul.es:
http://my.band.rul.es/?my_clear_key would clear the cache.

Cache auto clear

If you find painfull to manually clear the cache, you can use the auto-clear method,
Which makes sure the cache is cleared for a given period,which you should choose depending
on your website visits and you page modifications. This is set in the configuration variable (main/cache/auto_clear).
If you want to disable it just set it to auto_clear=no.
If you want to enable it specify a time in hours: @auto_clear=10@ to clear the cache every ten hours.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.