Thanks Chris for your patience:) Actually I'm diving into the code...I've found something that leaves a mess..
I'm debugging the entire code to have a notion of shindig - partuza interaction flow, and that is what I found.. gadgets.json.stringify function (..rps/wpm.transport.js) changes the entire rpc object structure... I mean that some fields of that object (i.e the array containing title, body and message type) are getting changed ...hence in my container.js (partuza's) in requestSendMessage function(that I should implement) I can get only the recipient, but no message to proceed. something is wrong with my code:( or I'm doing so.. On Dec 2, 3:13 pm, Chris Chabot <[email protected]> wrote: > On Wed, Dec 2, 2009 at 9:05 AM, Mel Morrow <[email protected]> wrote: > > > requestSendMessage: function() { > > > } > > > this is what I need.. > > Well, there you send stuff! :-) > > Really the implementation details are completely up to you, if you wanted to > add this functionality to partuza I would suggest adding a new controller > (partuza/Application/Controllers) that can receive the message post, and > just do a simple Ajax post to that url (suggestion: do include the security > token so you can validate it's not a abuse of the functionality, and can > retrieve or compare the app id and viewer id). > > I know that probably doesn't sound like a useful suggestion, but there's > just no replacing actually diving into the code and figuring it out to see > how it works -- You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" 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-container?hl=en.
