Mailing-List: contact cygwin-apps-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-apps-owner AT cygwin DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT cygwin DOT com>
List-Help: <mailto:cygwin-apps-help AT cygwin DOT com>, <http://sources.redhat.com/lists.html#faqs>
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Delivered-To: mailing list cygwin-apps AT cygwin DOT com
Subject: Pavel - more on URL's
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Date: Tue, 14 May 2002 00:04:48 +1000
X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
content-class: urn:content-classes:message
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C6094@itdomain003.itdomain.net.au>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
From: "Robert Collins" <robert DOT collins AT itdomain DOT com DOT au>
To: "Cygwin-Apps" <cygwin-apps AT sources DOT redhat DOT com>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g4DE5IY22110

You should also look at IOStreamProvider.h - this is how io stream
providers, which handle URL schemes register themselves. You can
leverage this to make the list of schemes pluggable (i.e. the
IOStreamProvider interface uses strings now, but should be converted to
URLScheme's etc). The current io_stream.cc code uses a pluggable list of
schemes, and I'd hope that that saves you a bit of coding (but where
list should sit is unclear. My feeling is that URLParser should be
unconcerned about known and unknown schemes but I'm not worried either
way).

Just ask if anything there is unclear).