[
Lists Home |
Date Index |
Thread Index
]
1/9/2002 4:34:58 PM, Tim Bray <tbray@textuality.com> wrote:
>
>This kind of thinking goes on all over the place. I call it
>the "junior-engineer-deciding-to-code-it-in-assembler-to-make-
>it-faster-without-measuring-first" fallacy. -Tim
That was certainly my reaction to the original article. The
discussion, however, has been quite enlightening about some of the
more subtle issues that RPC over HTTP in the real Internet must
face up to. Kurt Cagle in particular has made some
very interesting posts, especially concerning the difficulties
of working with sychronous programming paradigms in the
unreliable, bursty, unpredictable latency world of the Web.
http://lists.w3.org/Archives/Public/xml-dist-app/2002Jan/0117.html
"The question that I have is whether most of
the applications out there will be designed with an eye toward
asynchronicity, multi-threading, and other techniques to insure scalability,
and whether the fundamentally client/server architecture of RPC oriented web
services can in fact scale effectively in the face of tools that disguise
the fact that web services as written are synchronous.
This is less of a concern on the Java said than it is with the legion of VB
programmers out there who are still working with a point and click interface
as their primary interface mechanism. The notion of asynchronous listeners
in Java has been deeply ingrained in the language from the beginning.
.. [but] there are huge number of VB programmers that have only a vague
inkling of the way that event-based programming in general work, and their
tools of choice are essentially single thread apps. ...
the combination of being able to do synchronous .NET services
on the Internet transparently worries me more than a little."
|
