Re: Using the entity in a Filter

[Thierry Boileau]

Mail sent on the 08/28 and apparently lost. --- Hello Jim, you can have a look at this issue: http://restlet.tigris.org/issues/show_bug.cgi?id=149 The idea was to support the content-md5 standard header and to allow users to manually check the digest value of a representation. Here is the list of the additions:  - a Digest object in the org.restlet.data package that stores an algorithm and a value.  - a "digest" property on a Representation that contains the checksum of the representation computed according to an algorithm.  - a computeDigest(String) on a Representation that reads entirely the representation and computes the digested value  - two checkDigest methods on a Representation that ... checks the current digest value with the computed one.  - the API handles the mapping between the digest attribute of a representation (of the request or the response) and the "content-md5" header (the only supported by the HTTP RFC). As you may have noticed, there is no automatic way to check the digested value. The reason is that, as you point, there is a high cost and we were quite reluctant to "impose" that in a filter. The idea is to let you store the stream at your convenience and check the digested value when you want: in a filter, at the resource level. etc. best regards, Thierry Boileau Hi, I need to use the entity of a response to generate a digital signature in a filter before it is passed to the Router. AFAIK you can only call response.getEntity().getText() once. Is there way to do this from the Request object. cheers </jima>