Kevin, I presume you'll also be adding POST capability to _IG_Fetch?
We just can't write serious server-based applications without it. Thanks, Dan On Nov 29, 12:15 am, "Kevin Marks" <[EMAIL PROTECTED]> wrote: > url content type is not currently supported; most developers are using > _IG_Fetch at the moment; there are plans to make this more secure. > > On Nov 29, 2007 12:02 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > wrote: > > > > > Hi, > > I want to architect a rather heavy app where users would collaborate > > to generate a lot of content which can't really be stored and accessed > > using the persistence features provided by google's api. What would be > > the best way to build such an app. Here are my thoughts: > > > 1, Use the "url" content type to keep the files on my server. It would > > enable me to use server side scripting (perl/python....) on my server > > and It would lead to a better organization of files. > > 2. Whenever a page that has devependencies on both the data on my > > server, and social data from orkut needs to be shown to the user, use > > javascript calls to query orkut, and javascript _IG_Fetch requests to > > get data from my server, and use both of these to populate the html > > dynamically. > > > Do you see any limitations that this might impose. Does this approach > > give me enough freedom to build just about anything? It would be great > > having your feedback before I go ahead. > > > Thanks, > > -Niraj --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial API Definition" 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 -~----------~----~----~----~------~----~------~--~---
