Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
To:	cygwin AT cygwin DOT com
From:	Thorsten Kampe <thorsten AT thorstenkampe DOT de>
Subject:	Re: displaying Windows program on Linux via ssh / X?
Date:	Wed, 15 Jun 2005 08:47:29 +0100
Lines:	17
Message-ID:	<1js53aj9j9l8.19vbysot40wc2.dlg@40tude.net>
References:	<42AF2A0E DOT 2050804 AT mch DOT one DOT pl> <d8ncdh$dd1$1 AT sea DOT gmane DOT org> <42AF4E36 DOT 7070202 AT mch DOT one DOT pl>
Mime-Version:	1.0
User-Agent:	40tude_Dialog/2.0.15.1
X-IsSubscribed:	yes

* Tomasz Chmielewski (2005-06-14 22:37 +0100)
>> You are making an assumption that MS Windows was designed as a networked 
>> windowing system. It's not. It's not Cygwin's fault nor X windows fault 
>> rather it is MS' fault in that their concept of GUI windowed apps is not 
>> cleanly divided into the client/server paradigm.
> 
> No, I don't make any assumption that MS Windows can "stream" the display 
> in a client/server mode [...]

WTF? Windows applications simply aren't X clients. That's all.

For the "superiority" of the X window server/client concept you may
have a look at http://pepper.idge.net/disaster.html

The first thing everyone notices about this disaster is the braindead
exchange of the client/server terminology every else uses in
computing.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -