[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Categories of Web Service messages: data-oriented v

• To: "'xml-dev@l... '" <xml-dev@l...>
• Subject: Re: Categories of Web Service messages: data-oriented v
• From: Gavin Thomas Nicol <gtn@r...>
• Date: Sun, 10 Feb 2002 01:41:18 -0500
• In-reply-to: <3C660DE2.8111A9E9@p...>
• Organization: Red Bridge Interactive, Inc.
• References: <D7155AD41ECFD511AF4A00B0D0202CB51DFD7F@MAILHOST> <3C660DE2.8111A9E9@p...>

> But consider that for the last several years, programmers have spent
> a massive amount of effort figuring out how to make a "web
> interface" to their software. Web application frameworks, J2EE, ASP,
> PHP, etc. etc. Part of this is because people have spent the last
> few years remapping their problem domains into the REST model. 

I think the "web interface" here is important as a test of REST and 
HTTP applicability. Not everyone needs, or wants a web interface... 
though most people want to leverage ubiquitous networking easily.
At the end of the day, choice of architecture at this level is 
dictated by larger application architectures... and people should 
always remember that. Maybe HTTP/REST fits, maybe it  doesn't.

The best part of Roy's thesis is the definition and methodology of 
classifying and (subjectively) evaluating architectures. It provides a 
nice basis for experimenting with, discussing, and evaluating new 
network architectures and implementations thereof. It'd be interesting 
to see someone design a protocol explicitly optimised for the REST 
architecture... I'm picking it'd look something like BEEP.

• References:
  • RE: Categories of Web Service messages: data-oriented v
    • From: Michael Brennan <Michael_Brennan@A...>
  • Re: Categories of Web Service messages: data-oriented v
    • From: Paul Prescod <paul@p...>

• Prev by Date: Re: Categories of Web Service messages: data-oriented v
• Next by Date: Re: Documents within documents
• Previous by thread: Re: Categories of Web Service messages: data-oriented v
• Next by thread: SV: Categories of Web Service messages: data-oriented v saction-oriented
• Index(es):
  • Date
  • Thread