[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ircd.conf considerations / XML

To: jbn@xxxxxxxxxxxxxx
Subject: Re: ircd.conf considerations / XML
From: James Waldrop <sulam@xxxxxxxxxxxxx>
Date: Mon, 03 Aug 1998 11:25:31 -0700
Cc: Magnus Tjernstrom <d92-mtm@xxxxxxxxxxxx>, ircd-users@xxxxxxxxxxx
Organization: Construct Internet Design
References: <Pine.SUN.3.95.980731220727.8181A-100000@sister.ludd.luth.se> <35C4F1A8.CBA44274@obel.auc.dk>

Jørgen Nielsen wrote:
> Currently there is no other way than to do a preparser/converter IMHO. Would
> ofcourse be better to just built in an XML parser but that will have to wait I
> am sure.. don't want anyone to choke on the XML :)

Actually XML parsers are freely available via the W3C, so when the time
comes to support XML directly, the parser should not be an impediment.

-- 
James Waldrop
Chief Technical Officer			sulam@xxxxxxxxxxxxx
Construct Internet Design		http://www.construct.net

Follow-Ups:
- Re: ircd.conf considerations / XML
  - From: Jørgen Nielsen

References:
- ircd.conf considerations / XML
  - From: Magnus Tjernstrom
- Re: ircd.conf considerations / XML
  - From: Jørgen Nielsen

Prev by Date: Re: ircd.conf considerations / XML
Next by Date: Re: ircd.conf considerations / XML
Previous by thread: Re: ircd.conf considerations / XML
Next by thread: Re: ircd.conf considerations / XML
Index(es):
- Date
- Thread