- Revision
- 1948
- Author
- joehni
- Date
- 2011-11-12 11:54:53 -0600 (Sat, 12 Nov 2011)
Log Message
Improve docs regarding thread-safety. Add link to blog using XStream with GAE.
Modified Paths
Diff
Modified: trunk/xstream-distribution/src/content/annotations-tutorial.html (1947 => 1948)
--- trunk/xstream-distribution/src/content/annotations-tutorial.html 2011-11-03 21:19:39 UTC (rev 1947) +++ trunk/xstream-distribution/src/content/annotations-tutorial.html 2011-11-12 17:54:53 UTC (rev 1948) @@ -504,9 +504,10 @@ that may fail in this case.</p></li> <li><strong>Concurrency</strong> <p>XStream is not thread-safe while it is configured, thread-safety is only guaranteed during marshalling and -unmarshalling. However an annotation is defining a change in configuration that is now applied while object +unmarshalling. Unfortunately an annotation is defining a change in configuration that is now applied while object marshalling is processed. Therefore will the auto-detection mode turn XStream's marshalling process in a thread-unsafe -operation any you may run under certain circumstances into concurrency problems.</p></li> +operation. While XStream synchronizes the configuration modification, it cannot guard concurrent reads and you may run +under certain circumstances into concurrency problems.</p></li> <li><strong>Exceptions</strong> <p>XStream uses a well-defined exception hierarchy. Normally an InitializationException is only thrown while XStream is configured. If annotations are processed on the fly they can be thrown obviously also in a marshalling process.</p></li>
Modified: trunk/xstream-distribution/src/content/faq.html (1947 => 1948)
--- trunk/xstream-distribution/src/content/faq.html 2011-11-03 21:19:39 UTC (rev 1947) +++ trunk/xstream-distribution/src/content/faq.html 2011-11-12 17:54:53 UTC (rev 1948) @@ -590,9 +590,10 @@ <h2 id="Scalability_Thread_safety">Is XStream thread safe?</h2> <p>Yes. Once the XStream instance has been created and configured, it may be shared across multiple threads - allowing objects to be serialized/deserialized concurrently (unless you enable the auto.detection and processing of - annotations). Actually the creation and initialization of XStream is quite expensive, therefore it is recommended to - keep the XStream instance itself.</p> + allowing objects to be serialized/deserialized concurrently (unless you enable the + <a href="" to process annotations on-the-fly). Actually the + creation and initialization of XStream is quite expensive, therefore it is recommended to keep the XStream instance + itself.</p> <!-- ...................................................... --> <h2 id="Scalability_Memory">How much memory does XStream consume?</h2>
Modified: trunk/xstream-distribution/src/content/references.html (1947 => 1948)
--- trunk/xstream-distribution/src/content/references.html 2011-11-03 21:19:39 UTC (rev 1947) +++ trunk/xstream-distribution/src/content/references.html 2011-11-12 17:54:53 UTC (rev 1948) @@ -137,6 +137,7 @@ <h1 id="blogs">Blogs and Articles</h1> <ul> + <li>November 11th, 2011: <a href="" XStream with Google App Engine</a> by Chris Khoo</li> <li>January 22th, 2010: <a href="" XML and XStream</a> by Antonio Gonzalez</li> <li>September 1st, 2009: <a href="" PDFs with XStream and XSL-FO</a> by Brian J. Stewart</li> <li>January 13th, 2009: [German article] <a href="" XStream lassen sich Objekte einfach und schnell serialisieren</a> by David Petersheim</li>
To unsubscribe from this list please visit:
