Re: svn commit: r1072302 - in /subversion/trunk: ./ subversion/include/private/ subversion/libsvn_fs_fs/ subversion/libsvn_subr/ subversion/tests/libsvn_subr/
On Sat, Feb 19, 2011 at 13:47, <stefan2_at_apache.org> wrote:
> Author: stefan2
> Date: Sat Feb 19 10:47:16 2011
> New Revision: 1072302
> URL: http://svn.apache.org/viewvc?rev=1072302&view=rev
> Merge all changes (r1068724, r1068739) from the
> integrate-cache-item-serialization branch.
> These patches introduce a very simple, limited purpose
> serialization framework and use that to switch the
> caching API from data copying to the more generally
> applicable (de-)serialization mechanism.
> This makes all types of caches usable with all types
> of cacheable items.
Why serialize/deserialize mechanism is better than data copying
function? For me implementing dup function is much easier and better
for performance than serialize/deserialize. Is it possible to keep
both mechanism in inprocess cache?
Received on 2011-02-19 12:13:58 CET
This is an archived mail posted to the Subversion Dev