• From: David Brownell <david-b@p...>
• To: Ken MacLeod <ken@b...>, xml-dev@l...
• Date: Thu, 19 Apr 2001 10:45:52 -0700

> The only unique* component here is that the data passed as the content
> are represented in the calling language as compound/complex objects
> conforming to [little-s] schemas rather than streams of mime content.

That's what I'd call a marshaling API.  In this case, it'd be a policy-rich
layer over the "stream of MIME content" style APIs that already exist.

The XML-over-HTTP messaging would use those stream'o'MIME
calls directly, rather than with intervening policies for SOAP etc.

- Dave

• Follow-Ups:
  • Re: So what do SOAP and XML-RPC buy you?
    • From: Ken MacLeod <ken@b...>

• References:
  • RE: So what do SOAP and XML-RPC buy you? (was Re: Massive Cross-P ost:The State of XML-RPC, April 2001)
    • From: "Bullard, Claude L (Len)" <clbullar@i...>
  • Re: So what do SOAP and XML-RPC buy you? (was Re: Massive Cross-P ost:The State of XML-RPC, April 2001)
    • From: Ken MacLeod <ken@b...>

• Prev by Date: RE: Create XML with DTD in Java
• Next by Date: [ANN] Charity XML Bookshop launched
• Previous by thread: Re: So what do SOAP and XML-RPC buy you? (was Re: Massive Cross-P ost:The State of XML-RPC, April 2001)
• Next by thread: Re: So what do SOAP and XML-RPC buy you?
• Index(es):
  • Date
  • Thread