You could additionally just pop up an overlay on the container page if you didn't want to navigate the iframe away from the app and lose state.
If you come up with an api for this, make sure to post it to the spec discussion group! ~Arne On Dec 17, 9:56 pm, sonic <[email protected]> wrote: > hi, > I am working on implementing an opensocial container for a SNS site, > I met a problem that how to give opensocial application the ability to > let user can interact with a container domain page. I give the > following use case: some SNS sites support feature called virtual > currency(VC), user can buy VC using the real money, and spend their VC > on opensocial applications(for example, an application has VIP level, > user can buy VIP using VC), for security reason, the payment action > must happen in a container domain, not in opensocial apps domain. > My rough solution is: provide a special API, given > 'navigateToPaymentPage', the api will tell container page(via rpc) to > navigate the app iframe to a container payment page, user can deny or > grant the payment, then direct the iframe back to the application. > This is just my rough idea, I haven't got it implemented, want to > post here and hear your suggestions. thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
