You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Henning P. Schmiedehausen" <hp...@intermeta.de> on 2008/07/01 11:07:06 UTC
Re: Proposal : JSON backed canonical data set
"Louis Ryan" <lr...@google.com> writes:
Sounds nice. What, BTW is a "JSON DB Driver"?
Quick question: If you want to make the JSON example to behave like
coming out of a database (unless I got JSON DB driver wrong), why not
use a database? Just curious.
Ciao
Henning
>------=_Part_14110_31284130.1214612961651
>Content-Type: text/plain; charset=ISO-8859-1
>Content-Transfer-Encoding: 7bit
>Content-Disposition: inline
>Hi,
>I would like to propose a canonical data implementation for use in Shindig
>for unit and end-to-end testing based on a JSON structure that we check into
>SCM.
>The idea is pretty simple, define a JSON structure that contains the
>canonical data in the form described in the RESTful spec. Something like
>{ "people" : < an array of Person JSON objects>,
> "activities" : <an array of Activity JSON object for people>,
> "data" : <an array of app-data for people>,
> "friendLinks" : < a mapping between people id's to simulate friend links>,
> "dataLinks" : < a mapping between people id's and their app data>
>}
>This structure is loaded into a JSON DB driver and used to satisfy service
>requests. The driver will support CRUD operations on activities and data in
>line with the spec.
>Advantages:
>- Fully exercises the JSON side of the RESTful spec and its binding to POJOs
>etc
>- Supports simple mutability
>- Its canonical!
>- Shared between all the implementations
>Im working on creating some data which Ill send out if folks are interested
>-Louis
>------=_Part_14110_31284130.1214612961651--
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen
"Professor Peach in the library with the lead piping!" -- Donna
Re: Proposal : JSON backed canonical data set
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
"Louis Ryan" <lr...@google.com> writes:
>Think of a JSON structure like an untyped hierarchical entity DB as opposed
>to a flattened normalized relational one :)
Yep, my internal translator messed up "data base" and "data base
engine". Again. :-) I now understand what is the intention behind
this. Thanks for clarifying.
Ciao
Henning
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux,
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine guy
INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350
Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen
"Professor Peach in the library with the lead piping!" -- Donna
Re: Proposal : JSON backed canonical data set
Posted by Louis Ryan <lr...@google.com>.
Think of a JSON structure like an untyped hierarchical entity DB as opposed
to a flattened normalized relational one :)
On Tue, Jul 1, 2008 at 2:07 AM, Henning P. Schmiedehausen <hp...@intermeta.de>
wrote:
> "Louis Ryan" <lr...@google.com> writes:
>
> Sounds nice. What, BTW is a "JSON DB Driver"?
>
> Quick question: If you want to make the JSON example to behave like
> coming out of a database (unless I got JSON DB driver wrong), why not
> use a database? Just curious.
>
> Ciao
> Henning
>
>
>
> >------=_Part_14110_31284130.1214612961651
> >Content-Type: text/plain; charset=ISO-8859-1
> >Content-Transfer-Encoding: 7bit
> >Content-Disposition: inline
>
> >Hi,
>
> >I would like to propose a canonical data implementation for use in Shindig
> >for unit and end-to-end testing based on a JSON structure that we check
> into
> >SCM.
>
> >The idea is pretty simple, define a JSON structure that contains the
> >canonical data in the form described in the RESTful spec. Something like
>
> >{ "people" : < an array of Person JSON objects>,
> > "activities" : <an array of Activity JSON object for people>,
> > "data" : <an array of app-data for people>,
> > "friendLinks" : < a mapping between people id's to simulate friend
> links>,
> > "dataLinks" : < a mapping between people id's and their app data>
> >}
>
> >This structure is loaded into a JSON DB driver and used to satisfy service
> >requests. The driver will support CRUD operations on activities and data
> in
> >line with the spec.
>
> >Advantages:
> >- Fully exercises the JSON side of the RESTful spec and its binding to
> POJOs
> >etc
> >- Supports simple mutability
> >- Its canonical!
> >- Shared between all the implementations
>
> >Im working on creating some data which Ill send out if folks are
> interested
>
> >-Louis
>
> >------=_Part_14110_31284130.1214612961651--
>
> --
> Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux,
> 91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
> Open Source Consulting, Development, Design | Velocity - Turbine guy
>
> INTERMETA - Gesellschaft fuer Mehrwertdienste mbH - RG Fuerth, HRB 7350
> Sitz der Gesellschaft: Buckenhof. Geschaeftsfuehrer: Henning Schmiedehausen
>
> "Professor Peach in the library with the lead piping!" -- Donna
>