8 messages in com.freebase.developers[Developers] Using the Freebase.com c...
FromSent OnAttachments
Will MoffatMar 26, 2008 10:06 am 
Alec FlettMar 26, 2008 10:35 am 
brendanMar 26, 2008 10:36 am 
Will MoffatMar 26, 2008 4:13 pm 
John GiannandreaMar 26, 2008 4:25 pm 
Will MoffatMar 26, 2008 4:45 pm 
John GiannandreaMar 26, 2008 7:04 pm 
brendanMar 27, 2008 10:16 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[Developers] Using the Freebase.com client as an IFRAME your own web appActions...
From:Will Moffat (will@metaweb.com)
Date:Mar 26, 2008 10:06:46 am
List:com.freebase.developers

Hello,

I've seen a few Javascript developers (including myself) go through this process:

* write a cool Javascript Freebase app (like Zak's
http://dev.mqlx.com/~zak/arch/) * decide to give users the ability to edit data * decide you can't be bothered to re-implement the features of the Freebase.com client (and learn mqlwrite + setup an api proxy) * Take the path of least resistance and use a modal dialog IFRAME to display the topic in Freebase

This Freebase-in-IFRAME approach has two problems:

* How do we know if the user changed data? (We want to avoid rebuilding the state of a complex AJAX app if possible) The mwLastWriteTime cookie may have been updated, but it's inaccessible since the app isn't on freebase.com

* How do we get this changed data? Since the mwLastWriteTime cookie isn't set, re-running the MQL query won't give the latest data. You need to resort to cache-busting techniques like incrementing limit'

Any ideas about how to solve these problems? cheers, --Will