- From: Mark Baker <distobj@acm.org>
- Date: Thu, 17 Oct 2002 14:27:41 -0400
- To: David Orchard <dorchard@bea.com>
- Cc: www-ws-arch@w3.org
Alright, great to see it acknowledged by a Web services promoter!! I was happy to work with the existing Bass/Clements/Kazman definition, but much prefer Roy's. So does this mean that the desired properties of the Web services architecture is on the table for discussion? Which of REST's properties we don't want, etc.. If we get this stuff resolved, it should be a short trip to understanding why I believe Web services aren't up for the task they've been given. MB On Thu, Oct 17, 2002 at 11:01:35AM -0700, David Orchard wrote: > > Chapter 1 of RoyF's thesis talks about software architecture - > http://www.ics.uci.edu/~fielding/pubs/dissertation/software_arch.htm > > For example, a great definition of architecture is provided "A software > architecture is defined by a configuration of architectural > elements--components, connectors, and data--constrained in their > relationships in order to achieve a desired set of architectural > properties." > > On the "ilities" or properties of architectures are dsicussed in section 2 - > http://www.ics.uci.edu/~fielding/pubs/dissertation/net_app_arch.htm > > I can't resist being cheeky and point out that these are the first 2 > chapters of Roy's thesis, which has been listed as recommended reading for > some time. > > Cheers, > Dave -- Mark Baker, CTO, Idokorro Mobile. Ottawa, Ontario, CANADA. http://www.markbaker.ca http://www.idokorro.com
Received on Thursday, 17 October 2002 14:26:06 UTC