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,
-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
-~----------~----~----~----~------~----~------~--~---

Reply via email to