> It feels very much like RMI, although it's a document exchange
> system rather than a distributed object system. Developers should
be
> aware of that subtle distinction (although many aren't -- leading
to
> a variety of bad practices).
I would be interested in more information about why it "feels like
RMI" but acts like a "document exchange system".
Why does it feel one way, but act another?
If it feels a certain way, why should developers be aware that it is
acting some other way?
What has led to this confusion, what bad practices have resulted, and
what can be done to correct them?
This seems critical knowledge toward success with SOAP. Is it boiled
down somehwere, or why not, for better results with SOAP?
Thanks,
Patrick
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
