Lists Home |
Date Index |
Quoting Michael Brennan <Michael_Brennan@Allegis.com>:
> [... comments on EJB and REST snipped ...]
Interesting. I posted an item on the RESTwiki wish list asking to see
a worked example of how one would structure a typical Java/EJB application
In particular I think I think that a good worked example would be to
take the canonical "Java Pet Store" example used in the Sun Blueprints
and show how it can be made RESTful. Do you think thats something
worth working through?
To start things off, I've been assuming that being RESTful would imply
changes to the presentation layer only. The business logic remains
> I'm still absorbing REST, so I hope I'm interpreting things correctly.
> But if so, it seems to me that a framework along these lines could be a
> great aid to developers. It could also help broaden mindshare for REST by
> providing a framework that offers real value to developers -- namely a
> better way for modeling complex applications than that promoted by
> session-based toolkits.
Exactly, which is why I'm keen to see some worked examples that cover
familiar territory -- at least for us Java/EJB types! :)
On the topic of REST in general, I was in a presentation today with Akamai
where they discussed some of their newer caching systems. In some cases the
application may need to be tweaked to make best use of this -- however it
that a RESTful approach probably wouldn't, and hence would be amenable to
kind of ASP caching and be very scalable.