Hi. I would like to ask you something regarding the nature of hosting gadget's xmls...
We are still figuring out the internal aspects of opensocial, right now we are using shindig(php flavor) to add opensocial support to a social network site, initially we intend to control which applications users can add (based on the allowed features from the server) so users can not add any application from it's xml url but by choosing them from a collection. We are also thinking about grabbing those xml files from their original sites and hosting them on our servers (because of fear the original site may not be available occasionally, although if this case url-type apps wouldn't be available anyway)... so the same idea came for hosting thumbnails, screenshots and icons (parsing the app's xml)... then came the issue of hosting locale's xmls and how to cope in serving them by using proxies without modifications to the original xml file... Maybe we are getting off the trail by adding, modifying or even corrupting things opensocial is not supossed or intended to do... so I would really appreciate if you can give us some advice on this, either we have to keep a limit to this approach, go on, or completely rely on other sites content. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" 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-api?hl=en -~----------~----~----~----~------~----~------~--~---
