Proposal: Bring back the Global Data store

0 views
Skip to first unread message

Oleg Pylnev

unread,
Apr 17, 2008, 1:49:33 PM4/17/08
to opensocial-an...@googlegroups.com

Hello all

 

We would like to resurrect global data store for OpenSocial apps for following reasons

1)      It was requested by developers.

2)      Global Store is hosted by container so it is inherently faster than external feed(s)

 

Due to demand, Myspace has already implemented the global app data store via REST services and plans to expose it as JavaScript extension functions as well.

 

Regards,

Oleg Pylnev

Myspace.com

Brian Eaton

unread,
Apr 17, 2008, 2:35:13 PM4/17/08
to opensocial-an...@googlegroups.com
On Thu, Apr 17, 2008 at 10:49 AM, Oleg Pylnev <opy...@myspace.com> wrote:
> Due to demand, Myspace has already implemented the global app data store via
> REST services and plans to expose it as JavaScript extension functions as
> well.

Once you expose this as a javascript function, what will stop a
malicious user from deleting all of the data?

Zhen Wang

unread,
Apr 17, 2008, 2:41:48 PM4/17/08
to opensocial-an...@googlegroups.com
Global app data storage without server side support is too prone to
abuse to be useful. I don't find it necessary to bring back the
feature, either.

Arne Roomann-Kurrik

unread,
Apr 17, 2008, 2:54:08 PM4/17/08
to opensocial-an...@googlegroups.com
IIRC, the original design made Global App Data read-only from the JavaScript API for this reason.  The expectation was that once the server-to-server APIs launched, application authors would be able to set these values remotely.

~Arne


On Thu, Apr 17, 2008 at 11:35 AM, Brian Eaton <bea...@google.com> wrote:



--
OpenSocial IRC - irc://irc.freenode.net/opensocial

Louis Ryan

unread,
Apr 17, 2008, 3:13:43 PM4/17/08
to opensocial-an...@googlegroups.com
Oleg,

The choice here is whether this kind of data should be managed in a push model with global app data or a pull model with caching using some of the proposed enhancements to the gadget spec. If the need is to have a bunch of config data be available to all applications and have that data be managed by the gadget provider only, I would prefer to see this be part of the gadget preload & caching framework for which there should be a RESTful API to do cache management.

Orkut originally had such an implementation but removed it in favor of prefetching feeds and JSON data from URLs and caching it.

-Louis

Paul

unread,
Apr 25, 2008, 9:34:33 PM4/25/08
to OpenSocial and Gadgets Specification Discussion
We implement in conjunction with our REST API. Perhaps we can revisit
this.

~Paul

Cassie

unread,
Apr 27, 2008, 7:13:05 PM4/27/08
to opensocial-an...@googlegroups.com
I think this sounds like a great idea. This issue is not receiving much attention or consensus for 0.8 so I'm considering it closed for now. In 0.9 (especially after we get all get a chance to implement and work with restful) we should take another look at this.

Thanks.

- Cassie
Reply all
Reply to author
Forward
0 new messages