Hi Michael, this is very interesting, but I don't currently understand how REST would map to what we do in Resources.
Could somebody with a RESTful background help out? For now, I just have a faint feeling that a client/server architecture where an Eclipse Workspace is located on a server and a local client interacts with that workspace through an RPC-Style IResource API would likely *not* be RESTful, because the Eclipse Workspace maintains State (e.g. IResource#isSynchronized()) whereas a RESTful system needs to be stateless. Or am I misunderstanding? Cheers, -- Martin Oberhuber, Senior Member of Technical Staff, Wind River Target Management Project Lead, DSDP PMC Member http://www.eclipse.org/dsdp/tm > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On > Behalf Of Michael Scharf > Sent: Friday, October 17, 2008 6:11 PM > To: E4 developer list > Subject: [eclipse-incubator-e4-dev] [resources] REST > (Representational StateTransfer) > > In the call today some asked for some links to an introduction > to REST. Wikipedia is a good starting point: > http://en.wikipedia.org/wiki/Representational_State_Transfer > > Some important attributes of the RESTful approach is: > * Client-server > * Stateless > * Cacheable > * Layered > > Here is a podcast (~1h) introducing the REST concepts (and > some links): > > http://www.se-radio.net/podcast/2008-05/episode-98-stefan-tilkov-rest > e.g.: > http://www.infoq.com/articles/rest-introduction > > Michael > _______________________________________________ > eclipse-incubator-e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev > _______________________________________________ eclipse-incubator-e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/eclipse-incubator-e4-dev
