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

RE: The Protocol [was: Syntax] is API Fallacy

• From: "Jonathan Borden" <jborden@m...>
• To: "XML Developers' List" <xml-dev@i...>, "Ingargiola, Tito" <ti64877@i...>
• Date: Thu, 6 May 1999 22:26:28 -0400

Tito,

> > What I had suggested was to use
> > XML to marshal objects by value (MBV) which specifically gets around the
> > network roundtrip killer.
> >
> Actually, the idea of using XML as the means of achieving MBV doesn't seem
> too good to me.
>
> Why?  First, one of the great attractions of a distributed object
> system is
> precisely that I'm not typically zapping objects about the network, but am
> rather dealing with the more interesting objects in different
> address spaces
> by (remote) reference.  So, as an an application developer using corba, I
> really don't care too much how my corba implementation (as
> provided by Iona
> or whomever) does its business (e.g., marshalling).  I just care that it
> does it correctly and, hopefully efficiently.

	To David Brownell: I see your argument very clearly now. Sometimes, in
order to get things working efficiently you need to get concerned with
protocols. Fine grained object access across process boundaries is slow.
There is no getting around this. Sometimes it is alot more efficient to zap
a document across a network in one fell swoop and the zap back changes
rather than updating it character by character.
	Like any development system there are good and bad uses. Techniques such as
MBV help distributed object systems designers avoid the pitfalls of find
grained object access across process boundaries.


>
> Finally, I'm not convinced that a corba/RPC-style of remote method
> invocation is typically well suited to web-oriented interactions -- most
> things on the web can be treated naturally and efficiently as
> streams.  Why
> add the extra weight (which seems to buy me little) of corba to a
> domain in
> which it seems a mis-fit?
>
	Agreed, who needs it! Precisely what I am suggesting is that sending large
grained packets of information (e.g. documents) across the web is the proper
way to develop distributed object systems. I do believe there is a role for
object analysis and design and that object methodologies including interface
development can and should be applied to web development.

Jonathan Borden
http://jabr.ne.mediaone.net



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • RE: The Protocol [was: Syntax] is API Fallacy
    • From: "Ingargiola, Tito" <ti64877@i...>

• Prev by Date: Re: Java based XML parsers for server use.
• Next by Date: Re: XML-Conformant Programming Languages
• Previous by thread: RE: The Protocol [was: Syntax] is API Fallacy
• Next by thread: Re: The Protocol [was: Syntax] is API Fallacy
• Index(es):
  • Date
  • Thread