On 1/17/07, Gregg Wonderly <[EMAIL PROTECTED]> wrote: > I think it should be fairly obvious that "slow" on a network is almost always > related to "latency" of transfer/transport between systems. There are a > couple > of issues to consider, for me. One is connection setup time for a > transfer/transport operation. Many HTTP based systems will experience this > latency on every remote operation unless some very specific features of HTTP > are > configured/available.
That's no longer the case; persistent connections are pervasively supported and used and have been for many years. > The other is what coding/decoding is needed which > represents overhead in the exchange between remote systems. That's an issue too, yes. In general, I think the issues described in RFC 817, and the meta-issue of layering, is as much to blame as anything... though of course, for any particular protocol, the relative importance of the issues will vary. http://www.ietf.org/rfc/rfc817.txt > WS, REST and IIOP, because they lack mobile code FYI, REST includes a mobile code constraint; http://roy.gbiv.com/pubs/dissertation/rest_arch_style.htm#sec_5_1_7 Mark. -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Coactus; Web-inspired integration strategies http://www.coactus.com
