Jerome Louvel wrote:
Absolutely, that's why the "tag" property is only available on the
org.restlet.data.Representation interface. Also, the tag doesn't have to be
necessarily generated "based on" the content of the representation. If not,
you need a way to store this association because this tag has to be
persistent across calls.
Cool, so keeping it as a stateful variable in the representation, and
keeping the representation around for as long as the resource hasn't
changed would work.
I saw you used the MD5 algorithm to generate the tag. This is cool, we
should add that feature directly to the NRE/API:
http://restlet.tigris.org/issues/show_bug.cgi?id=149
That was another example of how the Java APIs don't do enough -- I have
to generate the hex representation myself?! (grrrr...)
Note that there is also a "Content-MD5" header that seems to overlap with
you usage of tags. I'm not sure why we have both in the spec:
http://www.rfcsearch.org/rfcview/RFC/2616.html#14.15
To use the spec language: you MAY use MD5 for the tag but you're not
obligated to. MD5 just has properties that lend itself nicely.
Chris
--
Chris Winters ([EMAIL PROTECTED])
Lead Software Developer
Vocollect Healthcare Systems
CONFIDENTIAL, PRIVILEGED COMMUNICATION: This e-mail is private and
intended for the addressee(s) only. It may contain privileged and/or
confidential information. If you have received it in error you are not
authorized to disseminate it in any manner; please delete it and any
copies and reply to the sender that it was misdirected.
