9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jonathan Sergent <sergent@IO.COM>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] circular logic (was webdav...)
Date: Mon,  4 Nov 2002 17:43:45 -0800	[thread overview]
Message-ID: <05C3B9E5-F060-11D6-BE3D-0003939B34F8@IO.COM> (raw)
In-Reply-To: <e04993ce13f45ec2fd65ad090a407258@plan9.bell-labs.com>

On Monday, Nov 4, 2002, at 14:27 US/Pacific, Russ Cox wrote:
> non-http protocols are dangerous.
> therefore we'll only allow http.

This is an oversimplification.  The companies that I know that have
this problem are actually in a situation where they have an internal
network that is not directly routed to the Internet at all, and all
traffic must pass through application-layer gateways (aka proxies).
The protocols which are proxied tend to vary.  But everyone proxies
HTTP in this environment.

There often isn't an intent to stop the use of other applications; just
no resources (time and money) to explicitly enable them.

It seems to me like this sort of thing is going away and becoming less
common, not more common.

(If everyone used Plan 9 and people could just import /net, this
problem wouldn't exist... people in these environments would just
tunnel everything over 9P!  Is this any more acceptable?)

> only http is allowed.
> therefore we'll tunnel everything over http.

So often this is a matter of resources; if the application developer
knows that in some situations only HTTP is allowed, but doesn't want to
write everything for both cases, said application developer will tend
to just do everything over HTTP so that it "just works" for people on
weird networks.


--jss.



  reply	other threads:[~2002-11-05  1:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-04 22:27 Russ Cox
2002-11-05  1:43 ` Jonathan Sergent [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05  3:34 Russ Cox
2002-11-05  2:51 presotto
2002-11-04 20:32 Skip Tavakkolian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=05C3B9E5-F060-11D6-BE3D-0003939B34F8@IO.COM \
    --to=sergent@io.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).