From owner-freebsd-isp Tue Sep 16 08:11:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA29183 for isp-outgoing; Tue, 16 Sep 1997 08:11:48 -0700 (PDT) Received: from ns1.flask.com (root@ns1.flask.com [207.67.43.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA29178 for ; Tue, 16 Sep 1997 08:11:43 -0700 (PDT) From: skat@flask.com Received: (from skat@localhost) by ns1.flask.com (8.7.6/8.6.12) id KAA16037; Tue, 16 Sep 1997 10:07:39 -0500 (CDT) Date: Tue, 16 Sep 1997 10:07:39 -0500 (CDT) To: Blaine Minazzi cc: ISP@FreeBSD.ORG Subject: Re: Active Server Pages In-Reply-To: <341E98A9.2B6A0705@denverweb.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ASP only affects the server platform. The ASP pages are still platform independent from client side, unless the content developers choose to use ActiveX components (that's another issue). What happens on the server (i.e., cgi, isapi, nsapi, w*api, etc.) were never platform independent to begin with (try porting a unix cgi to WinNT or MacOS platform). I'm sure I could come up with several reasons why I prefer not to use ASP, but if someone wants to use it, it is their choice and their nightmare. Shin On Tue, 16 Sep 1997, Blaine Minazzi wrote: > > > > This enters the world of proprietary standards (well, not standards since > > that would imply there is a standard) and becomes very difficult to > > implement. > > And the whole IDEA behind the http, java, and what has made the web so > popular, was to allow platform independent sharing of information. > Without this ability, we are right back to the ground zero of > interoperability. > > Oh well. Proof again that the G&S factor is the driving force of many > corporate decisions. > > Blaine >