Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of d.hobi@gmx.ch designates
 212.227.17.20 as permitted sender)
Subject: Re: Versioning question
References: <SQ.akWH.6BAThLftNih.1HRLE2@seznam.cz>
From: Daniel Hobi <d.hobi@gmx.ch>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <SQ.akWH.6BAThLftNih.1HRLE2@seznam.cz>
Message-Id: <ADAE7EC5-B5FA-4F21-9E99-7775192F8FCA@gmx.ch>
Date: Tue, 16 Apr 2013 16:44:22 +0200
To: "users@jackrabbit.apache.org" <users@jackrabbit.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

AFAIK, when using filedatastore, jackrabbit calculates a sha1 ckecksum over t=
he content of a file. The checksum will then be split up and used as folder/=
filename.=20

If you have 2 identical files, the checksum will be exactly the same resulti=
ng in one file on the disk.

Daniel

Von meinem iPhone gesendet

Am 16.04.2013 um 15:34 schrieb "Marek Slama" <mslama@email.cz>:

> Hello,
>=20
> I want to ask if Jackrabbit makes any space optimization when new version o=
f
> binary content is created. For example:
> I have file node F: I create version V1 and then version V2 but I actually=
=20
> do not check in my code if anything has changed.
> so V1 1.0 and V2 1.1 content are the same. Is binary content stored twice o=
r
> only once?
>=20
> ie. my versionable node is:
>             Node fileNode =3D documentNode.addNode(docxName, NodeType.NT_
> FILE);
>             fileNode.addMixin(NodeType.MIX_VERSIONABLE);
>             fileNode.addMixin(NodeType.MIX_CREATED);
>=20
> Thanks
>=20
> Marek
>=20
> =3D