In article [EMAIL PROTECTED],
Paul Rubin http://[EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] (Cameron Laird) writes:
Others have answered this at other levels. In elementary terms,
there truly is a difference, Paul, and one that's widely reified:
a desktop client-server application typically
[EMAIL PROTECTED] (Cameron Laird) writes:
application in the web app model (I haven't even touched on the whole
stateless HTTP being mapped to a stateful environment issue, or the
need to manage the local web server) actually buys you anything. I
.
Go ahead: touch on
Paul Rubin http:/...nvalid wrote:
[EMAIL PROTECTED] (Cameron Laird) writes:
application in the web app model (I haven't even touched on the whole
stateless HTTP being mapped to a stateful environment issue, or the
need to manage the local web server) actually buys you anything. I
.
Go
In article [EMAIL PROTECTED],
Paul Rubin http://[EMAIL PROTECTED] wrote:
.
.
.
I'm not sure what you're getting at in this context. You can write a
desktop app where the window system communicates with a gui toolkit
through
[EMAIL PROTECTED] (Cameron Laird) writes:
Others have answered this at other levels. In elementary terms,
there truly is a difference, Paul, and one that's widely reified:
a desktop client-server application typically listens through
one socket, which therefore constitutes an index of the
In article [EMAIL PROTECTED],
Chris Mellon [EMAIL PROTECTED] wrote:
.
[scores of lines
of vigorous debate]
.
.
Moreover, if you *don't* need global access or zero-deployment
(zero-deployment is
