xml-dev - RE: across varied servers

[Xiao Hu <mhu_97@yahoo.com>]

Thanks for the mail, Josh:
    Yes, you can use SOAP with any protocol u like to,
but the main reason for SOAP to come out is because
the growing needs of E-busniess through Internet which
is the weak area for COM or CORBA, in another word -
SOAP tries to solve problem and make remote Object
Reference more easy ... SO who-ever tries to use SOAP,
the first thing to think about it will be: XML/HTTP
sending/receiving, besides Internet, I do not think
lot of people want to use it, cause DCOM or COM/MTS
calls, CORBA/POA, RMI are more efficient than SOAP -
that's also most of the companies component ware
technologies ....... And I can agree with you about
COM+ only support, I talked with Jeff in VC++
conference in Santa Clara, also with Richard, they all
said COM+ SUPPORT ASYNCH calls, even for COM object, I
can very easily write a middle message router to make
ASYNCH CALL possible, ok it's simpliy like this:

create Observable object ( or publisher object in MS
word ) and Observer object ( or consumer object in MS
word ), in JAVA/CORBA - whenever Observable object
make some changes, the Observer object will catch the
changes by calling Update method in Observer. In
COM(+)/MTS world, just create a empty COM object with
a dual Interface, register this as a COM(+) package,
from Publisher side, call this Interface and send
message, and inside the package call another COM
object ( Proxy Message Routing object )which can send
an outgoing message to all the receiving Consumers,
for ALL THE SYNCH. calls, the messages are directed to
the consumer directly ( bypassing Proxy Object ), FOR
ALL THE ASYNCH CALLS, the proxy object will send the
messages to the consumers (a internal listed target
machines) with pinging the target first periodicaly
and whenever it's back on line, the messages will go
there right away, surely these messages could be
catched in the local repository database, and
combining with MSMQ or MQseries, it'll be more simple
to realize, AGAIN, COM(+) support ASYNCH CALLs, YES,
cheers.

mark@fintrack.com
212-680-8664/8663
646-872-7341(cell)

----- Original Message ----- 
> COM+ is just COM with some extra services -- Anyway,
> CORBA and DCOM calls are both *synchronous* methods,
> as are sockets.  I assume you really do want asynch.
> communication?  SOAP/XML-RPC is a more open,
standard
> way to make calls between systems supporting CORBA,
COM,
> or practically anything else.  Most SOAP
implementations
> are based on HTTP, though; and since your question
was
> about a way to send XML data, you are in the same
boat.
> 
> Making NT and Unix communicate over MSMQ/MQSeries is
> not nearly as difficult as you might think.  Both
products
> are, IMHO, very easy to use.  SMTP is also quite
easy,
> and using a database as a queue is also easy.  I
suggest
> you start with whichever one you prefer and try to
prototype
> it.  It's not tough..

From: "Joshua Allen" <joshuaa@microsoft.com>
To: <johns@syscore.com>; "'mark hu'"
<mark@fintrack.com>; "'Narayanan, Ramesh'"
<RNarayanan@panasonicfa.com>; "'Marcel Ruff'"
<ruff@swand.lake.de>; <xml-dev@xml.org>
Sent: Friday, July 07, 2000 7:55 PM
Subject: RE: XML across varied Servers


> Dave Winer's Definition:
> 
> "SOAP is an XML format, specification, and a set of
implementations that
> allow software running on disparate operating
systems, running in different
> environments to make procedure calls over the
Internet."
> 
> I think of it as a complement to COM or CORBA,
though, not
> necessarily a replacement.  SOAP doesn't have to run
over
> HTTP, BTW -- you can send and receive SOAP messages
over
> any transport you like.
> 

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail – Free email you can access from anywhere!
http://mail.yahoo.com/

***************************************************************************
This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/
***************************************************************************