Kees Jongenburger wrote:
> > - I was pondering about an yet another extra field on images 'checksum',
> >   which would store a checksum on the handle field (a suggestion of
> >   Daniel). This would make it easy to check if a image was uploaded
> >   already. 
> I don't see any benefit. uploading a new image will brake a checksum
> wha'ts the point?
> scilla uses some sort of key as an authetication string to perform a
> tranformation
> so <mm:image number="123" template="s(45)"/> will generate something
> that hides the conversion command while delaying the transformation.
> checksum's can't be used for that either since the transformation must
> be finished in order to calculate the checksum.

It has nothing to do with transformations. That issue was tackled, simply
using the 'ckey'.

The 'checksum' field would be on the 'images' node, which provides you with
some way to check if the same image was uploaded already. It is imaginable
that a person forgot about wether a certain image was uploaded
already or not. In other words this check-sum could be used to search by the
byte-array. It could also be used for automatic synchronization of a batch
of images (e.g. from a digital camera), and avoid duplicates. One could also
try to do this by file-name, but that is less absolute.

I didn't say this is extremely useful, and that one cannot do without, but
if we are to add new fields to the image-builder, we can as well forget
none... And this seems at least a little useful, and in certain situations
quite nice to have.

Michiel


-- 
Michiel Meeuwissen                  mihxil'
Mediacentrum 140 H'sum                [] ()
+31 (0)35 6772979         nl_NL eo_XX en_US



_______________________________________________
Developers mailing list
[email protected]
http://lists.mmbase.org/mailman/listinfo/developers

Reply via email to