Diff
Modified: trunk/xstream-distribution/src/content/faq.html (2105 => 2106)
--- trunk/xstream-distribution/src/content/faq.html 2013-08-27 07:17:46 UTC (rev 2105)
+++ trunk/xstream-distribution/src/content/faq.html 2013-08-27 07:21:29 UTC (rev 2106)
@@ -646,12 +646,12 @@
<li>XML parser technology in use: You should use a streaming parser like Xpp3 or StAX. DOM-based
parsers process the complete XML and create their document model in memory before the first converter of XStream
is called.</li>
- <li>Your object model: Is it necessary to keep the complete object graph in memory at once. As alternative you might
+ <li>Your object model: Is it necessary to keep the complete object graph in memory at once? As alternative you might
use <a href="" streams</a> or write custom converters that can load and save objects of your
object model on the fly without adding them to the object graph physically. As example see the implementation of the
<a href="" in combination with the
- <a href="" to keep
- parts of the object graph separate.</li>
+ <a href="" from
+ XStream's persistence package to keep parts of the object graph separate.</li>
<li>References: By default XStream supports references to the same object in an object graph. This implies that XStream
keeps track of all serialized and deserialized objects internally. These references are kept with WeakReferences, so that the
memory can be freed as soon as nobody references these objects anymore.</li>
To unsubscribe from this list please visit:
