My guess is that ifpc is still in "Lawyer Limbo". Give them some time to un-encumber this stuff.
IFPC is well done, but it's not magic. An experienced javascript coder could come up with an alternate implementation without too much trouble. IFPC uses a common technique to pass data from a child frame to it's parent. It does this by creating a third inner frame with the same domainname as the parent. See: http://www.julienlecomte.net/blog/2007/11/31/ for an example implementation.. On Thu, Dec 20, 2007 at 12:05:36AM -0800, William Waites wrote: > > Vision Jinx ha escrit: > > > > Upon querying Google on this I was told the following: "IFPC stands > > for interframe procedure call" > > This is progress, we've been able to expand the acronym. Unfortunately > we still know nothing about how this works. > > Question for the Google people frequenting this group: when can we > expect the ifpc.js source code to be released or documented? > > I assume that there must be plans for such a release, otherwise it > would be *incredibly* dishonest to claim to have contributed to an > open source software project and yet hold back a basic required > component. If there were no such plans it might mean that the Apache > Software Foundation had been duped into incubating a proprietary > software project. > > As it is, it means that Google gets to supervise all development in > this sphere, each page refresh on a developer's box causing a > footprint at Google (making it hard to work off-line). Google could > disable everybody's work instantly by simply making the URL for the > ifpc.js unavailable. > > Sure there are workarounds for this last, the obfuscated script could > be saved locally, but to even attempt to assert this type of control > over an ostensibly open source software project is mind-boggling. > > Question for the Apache Software Foundation (who may want to read the > rest of the thread for context): are you aware that the contribution > of Google to "shindig" rests and depends on a piece of obfuscated > javascript glue that resides only on Google's servers and is > undocumented in any way? > > Incroyable. > > -w > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Google Groups > "Implementing OpenSocial Containers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to [EMAIL PROTECTED] > For more options, visit this group at > http://groups.google.com/group/opensocial-container?hl=en > -~----------~----~----~----~------~----~------~--~--- > -- Paul Lindner hi5 Architect [EMAIL PROTECTED]
pgpjv5znyTNPK.pgp
Description: PGP signature
