[OS3 Proposal] Core Services Revamp
James Snell
and building off the themes established therein, I am also working on
proposals for a revamped collection of Common API services. Currently,
the OpenSocial specification defines the Cache Service and a number of
RPC-protocol mechanisms for discovery, Because the RPC protocol is
dropped, those can be dropped as well and the Cache service can be
simplified even further.
The attached document is *an initial first draft* describing three
core services, and a place holder for a fifth. Additional work needs
to be done to flesh this out fully, obviously, but I wanted to at
least get these on the table for discussion.
1. Revamped Application Data Service... this pulls the AppData service
from the Social API spec and models it as a Core Service with a
greatly simplified and more flexible interface.
2. Revamped Cache Service... this is a fairly minor modification and
simplification of the existing Cache service that removes the
requirement to encode the invalidated cache keys as JSON or XML.
Rather, each are listed directly in plain text, separated by
LF/CR/CRLF. Eliminates the extra, unnecessary, and ultimately
pointless JSON/XML parsing.
3. Introduces a new Persistent Query Service. This makes it possible
for a client to create persistent searches that can be independently
managed. Still quite a bit to define here, but the idea is to make it
easier for applications to perform a variety of data retrieval
operations that currently aren't easily supported in the API. For
instance, pulling up details for an adhoc but persistent grouping of
profiles, etc.
4. Will eventually proposal a new Proxy Service... which will provide
an interface for proxying requests to remote services with
authentication, caching, and conditional request mechanisms managed by
the server.
This is just a draft, posted for discussion purposes....
Expect additional information for each of the proposed new services in
the not too distant future.
Mark W.
James Snell
I am currently unable to log into the wiki. As soon as I am able I will get in and add everything. As for the ietf boilerplate, I use xml2rfc for all my standards draft stuff by default so it just Carries through to here... Feel free to ignore those bits.
Migration plan is forthcoming. I will post details for that in the time before the summit at the end of the month.
Use of PATCH can be augmented with the use of the already supported method override header. Support is ramping up for additional extension methods and the fact that there are other deployed production apps with support for patch (e.g. Some of the google apis) will help the picture improve further.
--
You received this message because you are subscribed to the Google Groups "OpenSocial and Gadgets Specification Discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msg/opensocial-and-gadgets-spec/-/qPIRMqwW0WgJ.
To post to this group, send email to opensocial-an...@googlegroups.com.
To unsubscribe from this group, send email to opensocial-and-gadg...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/opensocial-and-gadgets-spec?hl=en.
