[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[List Home]
|
Re: [eclipse-incubator-e4-dev] RE: Re: [resources] REST(RepresentationalStateTransfer)
|
- From: Patrick Mueller <pmuellr@xxxxxxxxx>
- Date: Tue, 21 Oct 2008 13:42:43 -0400
- Delivered-to: eclipse-incubator-e4-dev@eclipse.org
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer; b=3jFwuWmRovhQpAPOyODX9TwgN/O8ONxonF/u8uzK7l6YRkVAqiDOX993Lvnzkv6wCTxkTL87fu0SWoOss1DbMXtE2NkWCAP1BYdXlnD1STyMebtUFByTrsXEKw/md3krtm2czdXuEwvw8rspePqhER41aKKDTmiG2T6iX05ikAM= ;
On Oct 21, 2008, at 12:15 PM, David Carver wrote:
So, from your experience... does it make sense to
work on API being more RESTful or not?
If you follow the patterns and rules for creating a good REST
implementation, it's much easier to implement than an equivalant
SOAP web service. It's also much more tool friendly.
Actually, neither of these is considered true. The WS-* world, with
the tooling behind it in the enterprise tool sets, makes it fairly
easy to implement and use WS-* services.
The problem with WS-* is that it's considered brittle. Tight
coupling. "On the web", not "Of the web", in terms of things like
doing caching right. etc, etc.
REST is a good thing to look at, but keep in mind it's not simple.
I think one thing you can say about the "simple" aspect of REST, is
that the messages flows are much more straight-forward than WS-* -
less wrappers, etc. Designing it so that it actually IS simple to
use, is not simple. :-)
Patrick Mueller
http://muellerware.org/