Mailing-List: contact dev-help@cayenne.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cayenne.apache.org
Received-SPF: pass (athena.apache.org: domain of razumovsky.andrey@gmail.com
 designates 209.85.218.217 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=elqxgVrpe3jMz33VdTYs7R7HrUl/4THRNDEtv+wmqUXZO99xuOmaDsdiWKkvHvJ64e
         OdsAP4KfF045mxxCbarwUMirxCBVQlaJ8VqWjKbEU9TqvoZfcbNYWHw83c67KIdujpqk
         W6XAeG1WpgwtGT1GE7idMjPOV67bvGyHXdqQ4=
MIME-Version: 1.0
In-Reply-To: <7e3605160911181959m2c295560jd204a07a2badd957@mail.gmail.com>
References: <3219fff70911171126k24894bb9ke762ebb2804fa2d4@mail.gmail.com>
	<5adb61290911171153w37e83443sd8c52940b9d65e0@mail.gmail.com>
	<7e3605160911181959m2c295560jd204a07a2badd957@mail.gmail.com>
From: Andrey Razumovsky <razumovsky.andrey@gmail.com>
Date: Thu, 19 Nov 2009 11:21:26 +0300
Message-ID: <3219fff70911190021q5c83df7m6b504cb9ea9e46fc@mail.gmail.com>
Subject: Re: Plans for the future (aka 3.1 roadmap)
To: dev@cayenne.apache.org
Content-Type: multipart/alternative; boundary=001517447dc6ce002b0478b50cae

--001517447dc6ce002b0478b50cae
Content-Type: text/plain; charset=ISO-8859-1

I really want to have some "ROP AJAX client" too. Particularily, GWT ROP
CLient, so that we could work on Web client same way (but using async calls,
of course) we do it on ROP client. What I soon found is that currently ROP
client has very complicated logic, in fact it lives its own life. E.g. it
can do resolving lazy relationships as needed (and in the middle of
method!), which is impossible in asynchronous AJAX model. So I ended up
writing simple module that converts server-side objects to JSON.
Another problem is that unlike server-side objects, client-side objects do
not have a map for all properties (anyone knows why it was done so?),
therefore they cannot be resolved without Reflection, and GWT does not have
reflection. But, I really want to fix this in 3.1 as a step to unificate
server-side and client-side objects.
So, creating "GWT ROP Client" is a separate step, which contains several
ideas from ROP, but should have its own architecture.

2009/11/19 Kevin Menard <nirvdrum@gmail.com>

> On Tue, Nov 17, 2009 at 2:53 PM, Michael Gentry <mgentry@masslight.net>
> wrote:
> > On Tue, Nov 17, 2009 at 2:26 PM, Andrey Razumovsky
> > <razumovsky.andrey@gmail.com> wrote:
> >> --- ROP: unify client- and server classes. i really want to see classes
> that
> >> can work both on client and server someday.
> >
> > I've never used ROP, but a lot of us here are starting to look into
> > AJAX for use in our applications and I'm wondering if some kind of
> > AJAX/JSON support via ROP would be useful.
>
> We had an SoC project a few summers back that support WSDL for ROP.
> That may be your best bet and it is something I'd like to resurrect.
> Layering JSON on top of that should be rather straightforward.
>
> --
> Kevin
>


-- 
Andrey

--001517447dc6ce002b0478b50cae--