Re: SUMMARY: Running X/Mosaic from behind a firewall

• Mail folder: WWW Talk Jul-Oct 1993
• Next message: Christopher J. McRae: "ADD_ACL/DEL_ACL (was Re: Access Authorization)"
• Previous message: bryan d oakley: "HTML+ : questions, and a suggestion for a graph or tree tag"
• In-reply-to: Colin Panisset: "SUMMARY: Running X/Mosaic from behind a firewall"
• Reply: Jason B. Bluming: "Re: SUMMARY: Running X/Mosaic from behind a firewall "
• Reply: Marc VanHeyningen: "Re: SUMMARY: Running X/Mosaic from behind a firewall "

Message-id: <9309281623.AA18498@Mordor.Stanford.EDU>
To: Colin.Panisset@nms.otc.com.au (Colin Panisset)
Cc: www-talk@nxoc01.cern.ch
Subject: Re: SUMMARY: Running X/Mosaic from behind a firewall 
Phone: +1 408 246 8253; fax: +1 408 249 6205
In-reply-to: Your message of Mon, 20 Sep 93 15:03:46 +1000.          <9309200503.AA14410@ra.pad.otc.com.au> 
Date: Tue, 28 Sep 93 09:23:03 -0700
From: Dave Crocker <dcrocker@mordor.stanford.edu>
X-Mts: smtp

dumb idea, but I'll offer it anyhow:

There already is a mechanism for moving data across an arbitrary
number or kind of firewalls.

It's called email.

Specify a Mime content type for web exchanges and ship things via
email.  This will, no doubt, create performance problems in some
cases, but that can be attacked by making the firewall relays
more efficient or handle some addresses differently, etc.

The nature of firewalls is that they involve organizational policy,
so that limiting the number of mechanisms operating on a firewall
should help adoption.

Dave

P.S.  There needs to be email-based Web access, anyhow, since many
people don't have interactive access to the net, but DO have
email access.

d/