The way I've seen most production containers do this is that they return a rendered title string instead of the template and parameter map. I'm not sure about Shindig's default behavior, though - you may want to follow up on the Shindig mailing list to see if they have any best practices here.
~Arne On May 21, 4:11 pm, John <johnbar...@aol.com> wrote: > I'm writing both a desktop application and an OpenSocial container. > The desktop application uses the OpenSocial REST API's to retrieve a > list of Activities from the OpenSocial server. The way things are > currently setup, the Activities that get returned have the TitleId and > TemplateParams fields filled out, but not the Title field. How does > the desktop application use the TitleId to render the Title field? Or > should this be the responsibility of the server? > > (I'm implementing the OpenSocial container using Shindig.) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" group. To post to this group, send email to opensocial-api@googlegroups.com To unsubscribe from this group, send email to opensocial-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
