From owner-freebsd-current  Thu Apr 16 19:28:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id TAA21323
          for freebsd-current-outgoing; Thu, 16 Apr 1998 19:28:13 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from home.dragondata.com (toasty@home.dragondata.com [204.137.237.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA21313
          for <current@freebsd.org>; Fri, 17 Apr 1998 02:28:10 GMT
          (envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.8.8/8.8.5) id VAA20582;
	Thu, 16 Apr 1998 21:26:15 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199804170226.VAA20582@home.dragondata.com>
Subject: Re: Networking strategy for -current
In-Reply-To: <199804170021.KAA00609@cimlogic.com.au> from John Birrell at "Apr 17, 98 10:21:08 am"
To: jb@cimlogic.com.au (John Birrell)
Date: Thu, 16 Apr 1998 21:26:14 -0500 (CDT)
Cc: julian@whistle.com, current@FreeBSD.ORG, kjc@csl.sony.co.jp
X-Mailer: ELM [version 2.4ME+ PL31 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Julian Elischer wrote:
> > The ability of FreeBSD to handle various data streams in a 
> > prioritised and stable manner would be of great value to a 
> > lot of users.. (imagine if your FTP server didn't make your 
> > telnet sessions grind to a stop).
> 
> That would be neat.
> 

Imagine if one lame shell user couldn't spew 3mb/sec out my pipe, killing my
router, and my uplink's router? :)

And imagine if I could do this without messing with conversation limits on
my router? :)

Where do I send the check?

Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message