11 messages in com.googlegroups.opensocial-containerRe: IFPC!? Re: Getting this Shindig s...| From | Sent On | Attachments |
|---|---|---|
| John Panzer | 12 Dec 2007 09:28 | |
| Bonstio | 17 Dec 2007 11:07 | |
| Joeri Sebrechts | 18 Dec 2007 08:36 | |
| Vision Jinx | 18 Dec 2007 15:01 | |
| William Waites | 19 Dec 2007 11:52 | |
| Vision Jinx | 19 Dec 2007 12:23 | |
| William Waites | 20 Dec 2007 00:05 | |
| Paul Lindner | 20 Dec 2007 04:24 | |
| Fitz | 20 Dec 2007 05:52 | |
| Fitz | 20 Dec 2007 05:52 | |
| William Waites | 20 Dec 2007 07:07 |
| Subject: | Re: IFPC!? Re: Getting this Shindig started: First commit |
|---|---|
| From: | Vision Jinx (vjn...@gmail.com) |
| Date: | 12/19/2007 12:23:58 PM |
| List: | com.googlegroups.opensocial-container |
Hi William,
Some great questions here and I had looked into the IFPC already.
I noticed it back when Financial Gadgets, Gadget to Gadget Communication, and PubSub all started... I started seeing the extra parameter showing in my server logs. eg. &nocache=0&ifpctok=4972552804510448534
Upon querying Google on this I was told the following: "IFPC stands for interframe procedure call, and my guess is that one of the features that you're using (PubSub perhaps) is adding the token for interframe communication."
So maybe to partially answer your question, I don't believe this part of the API has been made available and there is still a lot of grey in the terms, as my current understanding is that script is still property of Google, while the downloadable scripts from the Subversion repository are the "Open Source" files as of present.
There are suppose to be more coming soon as things start to gain steam, but I am really not sure about that particular script as it may be integrated into Googles systems and needs to be rewritten for the Shindig project and licensing.
I could be way off on this, but this seems to be what I have found with like you say the limited info avail on it.
Cheers! Vision Jinx
On Dec 19, 12:52 pm, William Waites <wwai...@googlemail.com> wrote:
John Panzer ha escrit:
- Basic IFPC (gadget <-> container communication) support via inclusion of Google IFPC library
It seems a bit of a stretch to say that you have included IFPC support in this commit. Rather, it seem as though the line,
<script type="text/javascript" src="http://www.google.com/ig/ ifpc.js"></script>
has been committed a few times in several files.
Downloading that little bit of javascript and looking at it shows that some effort has been gone to in order to obfuscate its mechanism.
So what we have here is a Java parser for the well documented Gadget framework and some javascript implementing the container mechanism.
The Java parser is nice but could have been written from the docs, as anyone who wants to use another server-side programming language would has to do anyhow.
The container javascript is useful, especially for testing such an alternate server-side implementation.
The missing piece is what ties them together, without which none of this will work. It is even sullies otherwise clean code with comments like,
gadgets.js:684: /* Nasty hack to get around the hardcoded /ig/ ifpc_relay URL */
What gives?
The IFPC mechanism doesn't seem to be documented *anywhere*. Searches of the web and the newsgroups and mailing lists using more than one search engine turn up precious little save this very announcement.
Can we at least have some docs explaining what exactly IFPC is and how it works? Unobfuscated source would be nice too...
It would also be interesting to know what the ASF has to say about its projects depending on undocumented and obfuscated code.
Cheers,