Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Contact Us
Online Help
Domain Status
Man Pages

Virtual Servers

Topology Map

Server Agreement
Year 2038

USA Flag



Man Pages
XML::SAX::Tap(3) User Contributed Perl Documentation XML::SAX::Tap(3)

XML::SAX::Tap - Tap a pipeline of SAX processors

version 0.46

    use XML::SAX::Machines qw( Pipeline Tap ) ;
    my $m = Pipeline(
        Tap( "My::Reformatter", \*STDERR ),
    my $m = Pipeline(
        Tap( "| xmllint --format -" ),

XML::SAX::Tap is a SAX machine that passes each event it receives on to a brach handler and then on down to it's main handler. This allows debugging output, logging output, validators, and other processors (and machines, of course) to be placed in a pipeline. This differs from XML::Filter::Tee, XML::Filter::SAXT and XML::SAX::Distributer in that a tap is also a pipeline; it contains the processoring that handles the tap.
It's like XML::Filter::Tee in that the events are not buffered; each event is sent first to the tap, and then to the branch (this is different from XML::SAX::Dispatcher, which buffers the events).
It's like XML::SAX::Pipeline in that it contains a series of processors in a pipeline; these comprise the "tapping" processors:
            |                  Tap instance                |
            |                                              |
            |  Intake                                      |
            |  +-----+    +---------+        +---------+   |
 upstream --+->| Tee |--->| Stage_0 |--...-->| Stage_N |   |
            |  +-----+    +---------+        +---------+   |
            |         \                                    |
            |          \                          Exhaust  |
            |           +----------------------------------+--> downstream
            |                                              |
The events are not copied, since they may be data structures that are difficult or impossibly to copy properly, like parts of a C-based DOM implementation.
Events go to the tap first so that you can validate events using a tap that throws exceptions and they will be acted on before the tap's handler sees them.
This machine has no "Exhaust" port (see XML::SAX::Machine for details about "Intake" and "Exhaust" ports).

XML::SAX::Tap - Tap a pipeline of SAX processors

    my $tap = XML::SAX::Tap->new( @tap_processors, \%options );

    Barrie Slaymaker <>

    Copyright 2002, Barrie Slaymaker, All Rights Reserved
You may use this module under the terms of the Artistic, GNU Public, or BSD licenses, as you choose.

Barry Slaymaker
Chris Prather <>

This software is copyright (c) 2013 by Barry Slaymaker.
This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.
2013-08-19 perl v5.28.1

Search for    or go to Top of page |  Section 3 |  Main Index

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with ManDoc.