Hi, Paul, From: Paul Hammant [mailto:p...@hammant.org] > > You are not the first to ask for this, but it is significantly more > > complex than just a backend setting. [....]
> Yup, I didn't think about the SHA1 being different. I'll implement it > client-side, just ignore this request. Note that you will already profit from differential storage even when using compressed zips, as included images etc. should have an identical compressed storage if the user is just doing text edits). We got similar benefits at my former employer when we stored JAR files in SVN (archival of old revisions); especially small patches and hotfixes with only a few changed class files were transferred and stored efficiently. You could also transparently transform the zip into an uncompressed zip file before uploading it, thus getting more benefits from differential storage - at the possible loss of bit-for-bit identity if you try to recompress the zip again on download, as different implementations of the algorithms tend to give slightly different results, even for the same compression level. On the other hand, this could even improve storage on the server when configured with a high compression level, as the server side compression can then exploit inter-file redundancies in the zip file (if present), while zip itself compresses all files independently. Best regards Markus Schaber CODESYS® a trademark of 3S-Smart Software Solutions GmbH Inspiring Automation Solutions ________________________________________ 3S-Smart Software Solutions GmbH Dipl.-Inf. Markus Schaber | Product Development Core Technology Memminger Str. 151 | 87439 Kempten | Germany Tel. +49-831-54031-979 | Fax +49-831-54031-50 E-Mail: m.scha...@codesys.com | Web: codesys.com | CODESYS store: store.codesys.com CODESYS forum: forum.codesys.com Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915 ________________________________________ This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
