1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
Source: xmlstreambuffer
Standards-Version: 4.7.2
Maintainer: Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>
Uploaders:
Timo Aaltonen <tjaalton@ubuntu.com>,
Section: java
Priority: optional
Build-Depends:
debhelper-compat (= 13),
default-jdk-headless,
javahelper,
junit,
libmaven-bundle-plugin-java,
libstax-ex-java,
maven-debian-helper,
Vcs-Browser: https://salsa.debian.org/java-team/xmlstreambuffer
Vcs-Git: https://salsa.debian.org/java-team/xmlstreambuffer.git
Homepage: https://github.com/eclipse-ee4j/metro-xmlstreambuffer
Package: libstreambuffer-java
Architecture: all
Depends:
${maven:Depends},
${misc:Depends},
Recommends:
${maven:OptionalDepends},
Description: XML Stream Buffer
A stream buffer is a stream-based representation of an XML
info-set in Java. Stream buffers are designed to: provide
very efficient stream-based memory representations of XML
info-sets; and be created and processed using any Java-based
XML API.
.
Conceptually a stream buffer is similar to the representation
used in the Xerces deferred DOM implementation, with the crucial
difference that a stream buffer does not store hierarchical
information like parent and sibling information. The deferred
DOM implementation reduces memory usage when large XML documents
are parsed but only a subset of the document needs to be processed.
(Note that using deferred DOM will be more expensive than
non-deferred DOM in terms of memory and processing if all
the document is traversed.)
.
Stream buffers may be used as an efficient alternative to DOM where:
* most or all of an XML info-set will eventually get traversed; and/or
* targeted access to certain parts of an XML info-set are required
and need to be efficiently processed using stream-based APIs like
SAX or StAX.
|
