<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
 <channel>
  <title>s11n changelog</title>
  <link>http://s11n.net/rss/s11n-changes.xml</link>
  <description>This feed act as a sort of ChangeLog for s11n, so that users can keep track of changes going on in the trees without having to subscribe to the development lists.</description>
  <lastBuildDate>Wed, 31 May 2006 14:16:06 GMT</lastBuildDate>
  <generator>ListGarden Program 1.3.1</generator>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <item>
   <title>Retiring this RSS feed</title>
   <description>As it turns out, maintaining this RSS feed is more trouble than it's worth, so it will be retired. For those who are really interested in following changes to libs11n, the project mailing lists, especially the CVS list, are the best places to do so. Links to those can be found at &lt;a href="http://sourceforge.net/mail/?group_id=104450">http://sourceforge.net/mail/?group_id=104450&lt;/a>.</description>
   <pubDate>Wed, 31 May 2006 14:15:19 GMT</pubDate>
  </item>
  <item>
   <title>1.3.0: added ssh/http/ftp plugin</title>
   <description>The new url_ssh and url_wget plugins support deserialization over the ssh/http/ftp protocols. The ssh plugin also supports write support.</description>
   <pubDate>Wed, 01 Mar 2006 19:22:05 GMT</pubDate>
  </item>
  <item>
   <title>1.1.3: manual grows by 20 pages, passes the 100-page mark</title>
   <description>The library manual has grown by about 20 pages since the last release, and passed the 100-page mark for the first time ever. Several chapters have been added, including &quot;s11nlite specifics&quot; and &quot;memory management&quot;, and a couple older chapters have been moved around or rewritten for 1.1.</description>
   <pubDate>Sun, 14 Aug 2005 07:53:02 GMT</pubDate>
  </item>
  <item>
   <title>1.1.3: more header reorgs</title>
   <description>The various proxy header files have been moved from proxy/foo.hpp to proxy/(std|pod)/foo.hpp. Thus std-namespace containers can be found under s11n.net/s11n/proxy/std/CONTAINERNAME.hpp, and likewise for PODs.</description>
   <pubDate>Sun, 14 Aug 2005 07:51:36 GMT</pubDate>
  </item>
  <item>
   <title>1.1.3: s11nbrowser ported to 1.1</title>
   <description>The s11nbrowser tool (http://s11n.net/s11nbrowser/) has been ported to the 1.1 API. Requires 1.1.3 or higher.</description>
   <pubDate>Fri, 08 Jul 2005 12:36:46 GMT</pubDate>
  </item>
  <item>
   <title>1.1.3: s11n_api_marshaller, slight change</title>
   <description>This shouldn't affect any clients, but might affect one or two hard-core users out there: s11n_api_marshaller&amp;lt;SerType&gt; has changed to s11n_api_marshaller&amp;lt;NodeType,SerType&gt;. i'm not sure why it hasn't always been that way. The older approach did not allow per-NodeType specialization of SAM, which, while it hasn't yet proven to be necessary, might be useful at some point.</description>
   <pubDate>Fri, 08 Jul 2005 12:34:42 GMT</pubDate>
  </item>
  <item>
   <title>1.1.3: s11n_traits::cleanup_functor</title>
   <description>s11n_traits has been extended to include a cleanup_functor. This allows the library to properly clean up containers of unmanaged pointers which fail deserialization, including nested containers  (e.g. in list&amp;lt;map&amp;lt;int,T*&gt;&gt;, we can now properly guaranty that each T is deleted if the core has to destroy the outer list). This type of approach appears to be the only way which the library can guaranty no leaks in the case of throwing/propagating an exception when there are unmanaged pointers in the current branch of the in-deserialization tree. We can finally make  error/exception-safety guarantees which were sometimes impossible to give before.</description>
   <pubDate>Fri, 08 Jul 2005 12:27:44 GMT</pubDate>
  </item>
  <item>
   <title>1.1.3: exceptions support rewritten</title>
   <description>After too many concerns about maintainability of the mask-based exceptions support, it has been duly scrapped. The new support takes advantage of the new s11n_traits::cleanup_functor support.</description>
   <pubDate>Fri, 08 Jul 2005 12:26:19 GMT</pubDate>
  </item>
  <item>
   <title>1.1.3: s11nlite::micro_api</title>
   <description>This little helper class is useful when one wants to load or save the same basic type of Serializable repeatedly. It also provides simple buffering support.</description>
   <pubDate>Fri, 08 Jul 2005 12:23:56 GMT</pubDate>
  </item>
  <item>
   <title>1.1.3: s11nlite::simple_config</title>
   <description>This class provides client apps with a config file stored as ~/.SOMENAME.s11n. The object takes care of loading and saving. The client only needs to de/serialize data from/to the config's data node.</description>
   <pubDate>Sun, 03 Jul 2005 00:29:00 GMT</pubDate>
  </item>
  <item>
   <title>1.1.2: basic plugins support</title>
   <description>DLL support has been partially re-introduced. It isn't as well-tested as the older back-end, but it's a lot smaller and is independent of the factory layer.</description>
   <pubDate>Tue, 28 Jun 2005 20:28:22 GMT</pubDate>
  </item>
  <item>
   <title>1.1.2: buildable under Win32</title>
   <description>Ashran and i got the code building under WinXP tonight. :) Everything but the expat_serializer (not yet ported) and libzfstream support (ditto) appear to work. The test code even behaved exactly as its Unix counterpart. The source tree is not buildable out-of-the-box on Windows, but that will be automated as much as possible very soon.</description>
   <pubDate>Fri, 24 Jun 2005 23:24:42 GMT</pubDate>
  </item>
  <item>
   <title>1.1.0: exceptions support</title>
   <description>1.1 introduces an exceptions model similar to the one used by the std::iostreams library. The function s11n::throw_policy() comes in two forms, a getter and setter. It uses a bitmask to define hints to the framework about what types of errors should throw. Hints include i/o errors, failed de/serialization of an object, etc. Many algorithms have been updated to define specific behaviours in the face of exceptions.</description>
   <pubDate>Sun, 12 Jun 2005 13:35:22 GMT</pubDate>
  </item>
  <item>
   <title>1.1.0: reminder: DLL support does not yet work</title>
   <description>The factory layer was completely rewritten in 1.1.0 and doesn't yet internally support loading of DLLs. It will be rewritten or significantly refactored again, so don't get too used to the s11n::fac namespace. Not much client code works directly with the factory API, so this is expected to be a low-impact change.&lt;br>&lt;br>Loading of DLLs will come back sometime before 1.2, at least for Unix-like platforms.</description>
   <pubDate>Wed, 01 Jun 2005 21:10:35 GMT</pubDate>
  </item>
  <item>
   <title>1.1.0: class_name&lt;&gt; family of kludges removed</title>
   <description>The long-standing class_name&amp;lt;&gt; class and the kludges developed around it are now gone. The same functionality is now provided by additions to the s11n_traits&amp;lt;&gt; interface, and fits in much more cleanly with the framework than the older &quot;model&quot; did.</description>
   <pubDate>Fri, 27 May 2005 15:15:17 GMT</pubDate>
  </item>
  <item>
   <title>1.1.0: Major header reorgs</title>
   <description>The list of header changes, and how to accommodate porting from 1.0, is explained fully in the library manual.</description>
   <pubDate>Fri, 27 May 2005 15:12:29 GMT</pubDate>
  </item>
  <item>
   <title>1.1.0: All 3rd-party dependencies removed</title>
   <description>1.1 does not depend on any external libraries, as 1.0 does. It optionally supports libs11n_zfstream, for transparent zlib/bzip2 support, but it does not require it.&lt;br></description>
   <pubDate>Fri, 27 May 2005 15:10:09 GMT</pubDate>
  </item>
  <item>
   <title>1.1.0: new lite interface: client_api</title>
   <description>s11nlite is now implemented as a wrapper around a class called client_api&amp;lt;NodeType&gt;. That class can be extended by users to give them an s11nlite-like API with their own custom handling. This can be used, e.g., to introduce a networking layer on top of the conventional Serializers.</description>
   <pubDate>Fri, 27 May 2005 15:08:40 GMT</pubDate>
  </item>
  <item>
   <title>Welcome to the ChangeLog</title>
   <description>This RSS feed acts as an informal changelog notification channel. It will not be updated for every code-level change, but changes in functionality, new features, etc., will be briefly described via posts to this feed.</description>
   <pubDate>Fri, 27 May 2005 11:30:19 GMT</pubDate>
  </item>
 </channel>
</rss>
