>>>>> "Ken" == Ken MacLeod <[EMAIL PROTECTED]> writes:
Ken> A little background first. SAX modules come in three basic
Ken> flavors, "drivers" which generate SAX events (parsers are
Ken> drivers), "handlers" which consume SAX events (writers and
Ken> tree builders are handlers), and "filters" which are both
Ken> handlers and drivers.
Do any of these have a standard API, e.g., is there a SAX driver API
that all modules should provide?
If so I'd say reserve SAX::Driver, SAX::Handler & SAX::Filter & let
any implementations live directly undex SAX::. The three reserved
modules could just provide a standard import routine to an
implementation in, like so
use SAX::Handler 'SAX::My3LeethA|\|ld3r';
in the same way the DBI modules abstractes the DBD::* modules.
If not, then perhaps SAX::Driver*, SAX::Handler* etc in the same way
that Apache modules are Apache::Auth* etc.
--
Stephen
"There are those who call me... Tim"
