From: sameer <sameer@c2.org>
Message-Id: <199512050900.BAA29519@infinity.c2.org>
Subject: Re: Protocol API
To: new-httpd@hyperreal.com
Date: Tue, 5 Dec 1995 01:00:30 -0800 (PST)
In-Reply-To: <9512050822.aa22954@gonzo.ben.algroup.co.uk> from "Ben Laurie" at
 Dec 5, 95 08:22:12 am
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-new-httpd@apache.org
Precedence: bulk
Reply-To: new-httpd@apache.org

> Is there any reason that Apache shouldn't listen on multiple ports (and bind
> different protocols to each one)?
> 

	The thing is though, while SSL can't co-exist with non-SSL,
but S/HTTP can live on the same port as non-S/HTTP. (Hell, as far as I
understand, you can put S/HTTP through an SSL connection.. S/HTTP
seems to be a network layer above SSL.. [hm, I said "lawyer" there.. I
am too caught up in this whole patent licensing stuff])
	that fact could lead to confusion. Other than that confusion,
I don't see why not..

-- 
sameer						Voice:   510-601-9777
Community ConneXion				FAX:     510-601-9734
The Internet Privacy Provider			Dialin:  510-658-6376
http://www.c2.org/ (or login as "guest")		sameer@c2.org