SAX: How many interfaces?

[james anderson]

greetings,

David Megginson wrote:

> For SAX, how much does the number of interfaces and classes matter?
> My original plan was to have something like this in the *.sax package

i'm against limiting the number of interfaces apriori. put the handlers in an
inheritance hieracrchy, let the user bind the productions they wish to use to
specific classes with the desired, more complex behaviour. the behaviour of
those productions in which they have no interested remains bound to a generic
class which does "nothing". the application requires only load those classes it
actually uses, but it can make this decision at run-time... !

> public interface Parser {
>
>   public void setEntityHandler (EntityHandler handler);
>   public void setDocumentHandler (DocumentHandler handler);
>   public void setErrorHandler (ErrorHandler handler);
>
>   void parse (String publicID, String systemID)
>       throws java.lang.Exception;
>
> }

it would be better to bind the handlers by name, rather than to have a static
function space.

james,



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