Mark, Sorry, I didn't read the message carefully enough!
So yes, yes is yes.... Eric ----- Original Message ---- From: Mark Baker <[EMAIL PROTECTED]> To: [email protected] Sent: Friday, June 8, 2007 10:03:04 AM Subject: Re: [service-orientated-architecture] Software architecture Hey, I thought I said we wouldn't discuss REST in this thread, Eric! 8-) But I interpret your "Yes" there as agreeing with me, that these are useful models for evaluating architectures and architectural styles. Does anybody *dis*agree? Mark. On 6/8/07, Eric Newcomer <[EMAIL PROTECTED] com> wrote: > > > > Yes but the problem starts when comparing theory to practice - the discussion > tends to compare Web services as they are implemented with REST as its > defined in a thesis. > > Lots of implemented HTTP is not RESTful, either. > > Eric > > > ----- Original Message ---- > From: Mark Baker <[EMAIL PROTECTED] org> > To: service-orientated- architecture@ yahoogroups. com > Sent: Thursday, June 7, 2007 4:07:09 PM > Subject: [service-orientated -architecture] Software architecture > > > > > Perhaps we can all step back for a second... > > Let's - for a moment at least 8-) - forget about REST, WS-*, SOA, > etc.. and just talk about software architecture. Pete laid out a > summary (below) of how, IMO, it all works: how constraints on the > relationship between architectural elements induce certain > architectural properties. > > Can we agree that this is a useful way for evaluating architectures & > architectural styles? Or more exactly, can we agree that papers like > Perry & Wolf's "Foundations" , or chapter 1 of Roy Fielding's > dissertation, describe useful evaluation methodologies? > > Mark. > > On 6/7/07, Peter Lacey <[EMAIL PROTECTED] r que.com> wrote: > > I'll admit to a little trolling, but this is not hyperbole, it is not a > > matter of opinion, and it is not a blanket statement based on religious > > fervor. The fact is that there is a paper out there -- you know the one > > -- that analyzes all prevalent means of distributed computing and teases > > out the properties they exhibit and the design factors that brought > > about those properties. Then, emphasizing "constraint and understanding > > of the system context," applies those design factors (constraints) to a > > new architectural style such that the end result is a system that > > provably! exhibits the properties desired. Those properties being > > separation of concerns, scalability, reliability, visibility, > > performance, simplicity, and evolvability. > > > > ____________ _________ _________ __ Sick sense of humor? Visit Yahoo! TV's Comedy with an Edge to see what's on, when. ____________________________________________________________________________________Ready for the edge of your seat? Check out tonight's top picks on Yahoo! TV. http://tv.yahoo.com/
