Set pref at least may need to communicate with the container. Most
containers that support user prefs provide some kind of form UI for
setting them. For example, look at iGoogle. If a gadget sets
preferences programatically, the container needs to update the form
with the new values, or else it will be out of sync.
I think a container that handles user prefs would probably want to
bypass Shindig when saving them and post to an endpoint within the
container directly (using the user's login cookie or equivalent for
authentication). That's what we're doing, anyway. We're not using
AppData for UserPrefs though, and we haven't implemented messages
either, so I can't speak to that.
-- Tim
On May 12, 2009, at 11:59 AM, Jordan Zimmerman wrote:
As I've mentioned before, it seems odd to me to have set_pref() and
requestSendMessage() implemented via RPC in the container. Both of
these
methods need to communicate with the server. How can this be done
securely in the container? The container doesn't have access to
OAuth or
makeRequest().
Jordan Zimmerman
Principal Software Architect
831.647.4712
831.214.2990 (cell)
[email protected]
SHOP*COMTM
Shop Smart, Save Big(tm)
www.shop.com
This message (including any attachments) is intended only for
the use of the individual or entity to which it is addressed and
may contain information that is non-public, proprietary,
privileged, confidential, and exempt from disclosure under
applicable law or may constitute as attorney work product.
If you are not the intended recipient, you are hereby notified
that any use, dissemination, distribution, or copying of this
communication is strictly prohibited. If you have received this
communication in error, notify us immediately by telephone and
(i) destroy this message if a facsimile or (ii) delete this
message
immediately if this is an electronic communication.
Thank you.
