• To: xml-dev@l...
• Subject: Re: Entity resolution vs. URI resolution
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Thu, 24 Jan 2002 08:53:47 -0500
• In-reply-to: <878zaphx6q.fsf@n...>
• References: <3C4DE133.21C45105@s...> <878zaphx6q.fsf@n...>

At 11:03 AM -0500 1/23/02, Norman Walsh wrote:


>I maintain that adding a resolveURI(uri, baseURI) method to the SAX
>API is "the right thing".
>

While this is important I just can't see any reason to put this in 
SAX instead of in java.net. In fact, I think this constructor 
probably offers exactly the functionality you're looking for:


public URL(URL context,
            String spec)
     throws MalformedURLException

The signature may not be exactly what you want but it's not that far off.
-- 

+-----------------------+------------------------+-------------------+
| Elliotte Rusty Harold | elharo@m... | Writer/Programmer |
+-----------------------+------------------------+-------------------+
|          The XML Bible, 2nd Edition (Hungry Minds, 2001)           |
|              http://www.ibiblio.org/xml/books/bible2/              |
|   http://www.amazon.com/exec/obidos/ISBN=0764547607/cafeaulaitA/   |
+----------------------------------+---------------------------------+
|  Read Cafe au Lait for Java News:  http://www.cafeaulait.org/      |
|  Read Cafe con Leche for XML News: http://www.ibiblio.org/xml/     |
+----------------------------------+---------------------------------+

• Follow-Ups:
  • Re: Entity resolution vs. URI resolution
    • From: Norman Walsh <ndw@n...>

• References:
  • Entity resolution vs. URI resolution
    • From: Edwin Goei <edwingo@s...>
  • Re: Entity resolution vs. URI resolution
    • From: Norman Walsh <ndw@n...>

• Prev by Date: RE: Strategies for a lowly XML document
• Next by Date: Re: Generality of HTTP
• Previous by thread: Re: Entity resolution vs. URI resolution
• Next by thread: Re: Entity resolution vs. URI resolution
• Index(es):
  • Date
  • Thread