Mailing-List: contact deltacloud-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: deltacloud-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of razorinc@gmail.com designates
 209.85.161.47 as permitted sender)
References: <1320275294-16956-1-git-send-email-lutter@redhat.com>
In-Reply-To: <1320275294-16956-1-git-send-email-lutter@redhat.com>
Mime-Version: 1.0 (iPad Mail 8G4)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <84AB9E17-409C-4BBF-9BDA-9A24B4DF7986@gmail.com>
Cc: "deltacloud-dev@incubator.apache.org"
 <deltacloud-dev@incubator.apache.org>, Doug Davis <dug@us.ibm.com>
From: Francesco Vollero <razorinc@gmail.com>
Subject: Re: Sketch of CIMI model layer
Date: Thu, 3 Nov 2011 14:07:25 +0100
To: "deltacloud-dev@incubator.apache.org"
 <deltacloud-dev@incubator.apache.org>


Sent from my iPad

On 03/nov/2011, at 00:08, lutter@redhat.com wrote:

>=20
> This patch is a first attempt at a CIMI model layer. Such a layer is neede=
d
> to deal with deserialization (and possibly serialization) of CIMI model
> objects from (to) XML/JSON, and to give us a place to stash business logic=

> connected to model classes.
>=20
>=20

>=20
> Another sidenote: since the CIMI API isn't terribly HTML friendly (e.g.,
> POST's all have XML or JSON bodies), I wonder if the HTML frontend
> shouldn't be a JS app that communicates with the server via JSON only.

Indeed, is more easy to manage JSON Objects from Javascript, and is quite si=
mple as well.

cheers,
Francesco

>=20
> David