agreed, except this part:

- user brings up the modal dialog for a topic and edits something - freebase.com last write cookie set (though they will be asked to login, inline, if not already logged in) - user closes the dialog and refreshes the mjt/js app browser window - ajaxy mqlread is issued, freebase.com last write cookie is used and observed, cache is invalidated

right? archiportal doesn't proxy anything, if the user is signed in, the browser freebase.com cookies are used and subsequent mqlreads use the same cookies.

that said, Zak and I tried having the archiportal screen refresh automatically whenever a user returns from using the modal iframe. It sucked because, as you've pointed out, even if the user doesn't do a write, now you have to wait around for all the freebase and google api calls to be made which takes several seconds.

I'd like to see a solution for this too because I think this kind of pattern is pretty sound, dare I say "lazy in a good way?". Writes are more difficult to implement and aren't done that often by the user, so it allows someone to build a mashup spending their time coding the part that is used the most. Also, on the read/write side, as the architecture schema is extended, the freebase.com client automatically keeps up.

Brendan

On Mar 26, 2008, at 10:07 AM, Will Moffat wrote: