[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: Parser Interface -- Summary of Change Requests

• From: "Don Park" <donpark@q...>
• To: "David Megginson" <ak117@f...>, "xml-dev Mailing List" <xml-dev@i...>
• Date: Sun, 1 Feb 1998 14:50:16 -0800

David,

>1) Allow SAX to work with an input stream as well as a URI.
...
>     void parse (String publicId, String systemId, InputStream input)
>       throws java.lang.Exception;
...

My suggestion would be to add following two methods to the EntityHandler
interface:

    public InputStream
getEntityByteStream (String systemID)
    throws Exception;

    public InputStream
getEntityCharStream (String systemID)
    throws Exception;

The parser implementation should invoke getEntityCharStream first to see if
the there is decoded data available.  If not, it should invoke
getEntityByteStream to get the raw data.

If both methods return null, then default URL based code is used.

>2) Simplify handler chaining by adding get* methods for existing
>   handlers.
...
>   This seems like a generally good idea (as will as a simple and
>   backwards-compatible change), and I am willing to implement it.
>   The only complication is that we'll have to define the default
>   state -- is the parser always required to return a default handler
>   if the user has not explicitly set one, or should it return null?


It would be up to the SAX implementation.  It might provide default
implementation depending on configuration.  For example, FooSaxDriver might
have setInputType() method which would install a default EntityHandler for
fetching XML document from a database.

BTW, You left out my other suggestion which was

>>>>>>>>>>>>>>>>>>>>>>>>
In addition, I would like to have following two methods added to the Parser
API for driver-specific operations:

    public Object getDriverProperty(String name);
    public Object setDriverProperty(String name, Object value);

Property names should be prefixed with some unique values to avoid confusing
other drivers.  Note that above methods can be invoked without knowing which
driver is actually being used.  For example:

    parser.setDriverProperty("SuperDriver.lowercaseElements", Boolean.TRUE);
    parser.setDriverProperty("HungryDriver.cacheSize", new Integer(100000));
<<<<<<<<<<<<<<<<<<<<<<<<

Above two methods allow driver-specific code without actually having to
import anything.

Regards,

Don Park



xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: Parser Interface -- Summary of Change Requests
    • From: David Megginson <ak117@f...>

• Prev by Date: Re: First experiences with XSL
• Next by Date: Re: SAX: Parser Interface -- Summary of Change Requests
• Previous by thread: SAX: Parser Interface -- Summary of Change Requests
• Next by thread: Re: Parser Interface -- Summary of Change Requests
• Index(es):
  • Date
  • Thread