If you want two apps to talk to one another and want to require the user to have both (ie, one cannot live without the other), then why not just make it one app?
I'm wondering too, what kind of use cases you had in mind. On Nov 6, 1:42 pm, Suhail Doshi <[EMAIL PROTECTED]> wrote: > I can, perhaps you would like two applications to talk to one another > but require the user to have both. > > On Nov 6, 11:22 am, "Arne Roomann-Kurrik (Google)" > > > > <[EMAIL PROTECTED]> wrote: > > I've added this as a feature request > > athttp://groups.google.com/group/opensocial-api/web/opensocial-feature-... > > > Can you elaborate on a use case that you see needing this function > > for? > > > Thanks, > > ~Arne > > > On Nov 6, 9:32 am, melvster <[EMAIL PROTECTED]> wrote: > > > > I would like to propose a listUserApps function that will allow an app > > > to be aware of other apps that the user has. This is the equivalent > > > of listing the process table in UNIX and has obvious advantages, for > > > the container that allows this functionality. > > > > Thoughts?- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Developers" 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 -~----------~----~----~----~------~----~------~--~---
