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

RE: Categories of Web Service messages: data-oriented vs acti

• To: "'michael.h.kay@n...'" <michael.h.kay@n...>, "'Paul Prescod'" <paul@p...>, xml-dev@l...
• Subject: RE: Categories of Web Service messages: data-oriented vs action-oriented
• From: Michael Brennan <Michael_Brennan@A...>
• Date: Tue, 5 Feb 2002 15:44:49 -0800
• Cc: "'Roger L. Costello'" <costello@m...>

> From: Michael Kay [mailto:michael.h.kay@n...]

<snip/>

> Exactly. It's not a data-only message, it's data with an 
> action attached to
> it. I prefer where possitble to represent the action as part 
> of the message
> rather than as part of the protocol at the next level down 
> the protocol
> stack.

I think there are two advantages to this approach over having the action
specified at the protocol layer.
1) You don't have to redefine how to represent the action for each protocol
binding used.
2) You can have richer messages where actions apply to portions of a
message, rather than just one action for the entire message.

However, this approach also has a disadvantage:
1) A message dispatcher must sniff the content of the message to discern its
intent. A protocol-level indicator can help optimize some level of message
dispatching, where dispatching can be done without having to parse the XML
in the message.

• Follow-Ups:
  • Re: Categories of Web Service messages: data-oriented vs action-oriented
    • From: Paul Prescod <paul@p...>

• Prev by Date: RE: Categories of Web Service messages: data-oriented v s action-oriented
• Next by Date: Re: Using <choice> to enforce rules
• Previous by thread: RE: Categories of Web Service messages: data-oriented vs action-oriented
• Next by thread: Re: Categories of Web Service messages: data-oriented vs action-oriented
• Index(es):
  • Date
  • Thread