Very interesting discussion indeed. I've been experimenting with
building visual REST applications – I used a
href=http://www.frevvo.com;frevvo/a and
a href=http://www.restlet.org;Restlet/a (I work for frevvo). I've
posted a couple of blog articles about my experiences and I'm definitely
On 4/11/07, Vincent [EMAIL PROTECTED] wrote:
[...]
I think it's helpful to think in terms of fundamental, base
resources and composite, view resources.
[...]
For other cases, I think it makes more sense to have the facets more
or less completely disjoint. The human useful, composite views
On 4/12/07, Jerome Louvel [EMAIL PROTECTED] wrote:
[...]
What is essential is that your core domain model is well defined and reused
by all your view resources. This core domain model can also be distributed
and implemented as RESTful resource if you can afford this flexibility.
FWIW, I think
Hi Vincent,
You add a query parameter with an URI to return to after edition:
/orange/editor?return=/main?orange=pictureapple=text
But maybe the page you return to depends on the result of the
operation. It's not a decision the client can make.
Ok, in this case your /orange/editor
Vincent vincent.lari at yahoo.ca writes:
Hi Matthieu,
Hello Vincent
You'll find comments within the text below. Best regards,
Basically I've a rich client application (Flex) accessing
Ah, but it's quite a different story, as the final (visual) representation is
assembled on the
Hi Vincent,
No it wouldn't make sense. You would instead directly
modify the Orange
resource, either directly from the browser or via some
edition pages (to
allow multi-page edition for example).
But then how you return to the main page after you've
modified the orange?
You add
Hi Matthieu,
Basically I've a rich client application (Flex) accessing
Ah, but it's quite a different story, as the final (visual) representation is
assembled on the client, not on the server.
I considered each resource as
being kind of a virtual web page, with one URI and one (or
John,
I think it's helpful to think in terms of fundamental, base
resources and composite, view resources.
[...]
For other cases, I think it makes more sense to have the facets more
or less completely disjoint. The human useful, composite views may
make a lot more sense to the user if
Hi John,
[...]
I think it's helpful to think in terms of fundamental, base
resources and composite, view resources. An analogy is the
difference between tables and views in a relational database such
as Oracle.
I agree, this is a useful analogy.
As you noted, in your example, it could
Hi Vincent,
So you're forcing one resource to be aware of other resources
just because of
the way your user interface in designed. If you switch to
HTML frames, you no
longer need these dependencies because each frame displays
only one resource
(the content frame, the profile frame,
I agree and would add that those lower-level resources (or core resources)
could be modelled and exposed as either:
- persistent POJOs (db4o, EJB3, etc.)
- RESTful resources (via a separate Restlet application for example)
In the second case, you could even think about a two-layer
,
Jerome
-Message d'origine-
De : Jeff Walter [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 11 avril 2007 06:19
À : discuss@restlet.tigris.org
Objet : Question to all about visual webapps and Restlet
Hey All,
Little philosophical/architectural question here...
I'd like to know how
On 4/10/07, Jeff Walter [EMAIL PROTECTED] wrote:
[...]
I'd like to know how many other people are using Restlet to build visual web
applications, and how they feel about aggregating resource data on their
pages?
What do you mean by visual web applications? I'm going to presume
that you mean
13 matches
Mail list logo
