New Features as of Version 0.72 PicklingTools 4 does NOT work with PicklingTools 7 : Thus the major version change. Any applications (such as SSGS versions < 2.21.4) using PicklingTools4 should make sure they update. SSGS version 2.21.4 and above should work fine with PicklingTools 0.71 or 0.72 Initially we were going to support both, but that's more problematic than simply upgrading. Added support for X-Midas : Included the entire X-Midas option tree "ptools" to show how to build an X-Midas C++ primitive that uses the MidasTalker. OpenContainers 1.4.1 has been updated to support use with X-Midas (in particular, the define -DOC_SUPPORT_XM). There are example primitives, build options and explain files included in the option tree. *****POTENTIAL INTERFACE CHANGE***** Changed the default to be WITHOUT Numeric : Due to some formats of Numeric not being supported, we changed the default serialization to be PythonNoNumeric on the MidasTalkers and most components. You have to specifically ask for Numeric in a MidasTalker or OpalPythonDaemon. Normally we hate changing defaults like this, but it's caused a number of problems for people not understanding why it was failing. PythonNoNumeric is more likely to work: once you get it working, you can add Numeric if you like to see if works for you. *****POTENTIAL INTERFACE CHANGE***** Made the constructors for MidasTalker less confusing (hopefully): The fourth parameter in the MidasTalker (for both Python and C++) is confusing: Serialization. The only purpose was to allow a MidasTalker to avoid serialization and just send ASCII strings. Added a new constructor that uses the more informative field "send_strings_as_is_without_serialization" field, and deprecates the other constructor with a warning. Added "cleanUp" to the MidasTalker : There was a request to expose the close routine so that a user can manually close the sockets if necessary. The "cleanUp" routine on the MidasTalker (.cc,.py) does that.