After looking at the code, I think you can take that comment out. The idSpec userId field can be an array of userIds or just one userId. jsoncontainer should be allowing this so it should be all good.
- Cassie On Wed, Jun 11, 2008 at 10:15 AM, <[EMAIL PROTECTED]> wrote: > Author: chabotc > Date: Wed Jun 11 10:15:40 2008 > New Revision: 666737 > > URL: http://svn.apache.org/viewvc?rev=666737&view=rev > Log: > SHINDIG-378 update broke requestSendMessage() patch from bruno > > Modified: > incubator/shindig/trunk/features/opensocial-current/jsoncontainer.js > > Modified: > incubator/shindig/trunk/features/opensocial-current/jsoncontainer.js > URL: > http://svn.apache.org/viewvc/incubator/shindig/trunk/features/opensocial-current/jsoncontainer.js?rev=666737&r1=666736&r2=666737&view=diff > > ============================================================================== > --- incubator/shindig/trunk/features/opensocial-current/jsoncontainer.js > (original) > +++ incubator/shindig/trunk/features/opensocial-current/jsoncontainer.js > Wed Jun 11 10:15:40 2008 > @@ -57,11 +57,16 @@ > }; > > JsonContainer.prototype.requestSendMessage = function(recipients, message, > - opt_callback) { > + opt_callback, opt_params) { > opt_callback = opt_callback || {}; > - > + opt_params = opt_params || {}; > +/* > + * TODO: Supporting just one IdSpec, but spec says Array.<String>, String > + * recipients Not sure how to implement it > + */ > + var id = new opensocial.IdSpec({'userId' : recipients}); > var req = opensocial.newDataRequest(); > - req.add(this.newRequestSendMessageRequest(recipients, message), 'key'); > + req.add(this.newRequestSendMessageRequest(id, message), 'key'); > req.send(function(response) { > opt_callback(response.get('key')); > }); > > >
