-remddt
template: pers?clnt=<name|pass>&com=remddt&whr=<where_pattern>
          Order of query params is not important.
pattern : * | <SQL part following WHERE>. The '*' means all.
          A special syntax must be used: ':' for = and '|' for <space>.
          This is because spaces and '=' are replaced in WWW requests.
          Note that string values must be enclosed in single quotes.
descript: removes all decay data records specified by 'whr' query
          parameter. If no matching records are found no records
          will be deleted (200 OK will still be returned). If the
          error code 401 is returned then no record has been deleted.
          Note that the 'remftr' command has also the effect of
          removing records of the corresponding features from this
          table, due to referential integrity constraints.
example : pers?clnt=name|pass&com=remddt&whr=dd_user:'us101'
          pers?clnt=name|pass&com=remddt&whr=dd_feature|like|'page9.%'
          pers?clnt=name|pass&com=remddt&whr=dd_timestamp>1005854664588
          pers?clnt=name|pass&com=remddt&whr=*   (deletes everything in table)
returns : 200 OK, 401 (fail, request error), 501 (fail, server error)
200 OK  : in this case the response body is as follows
          <?xml version="1.0"?>
          <?xml-stylesheet type="text/xsl" href="/resp_xsl/rows.xsl"?>
          <result>
          <row><num_of_rows>number of relevant rows</num_of_rows></row>
          </result>
comments: the reference to the xsl file allows to view results
          in a web browser. In case the response body is handled
          directly by an application and not by a browser, this
          reference to xsl can be ignored.
          Note that if a user is to be removed from the personal mode,
          the requests 'remddt' and 'remndt' should be called to remove
          decay data and numeric data respectively, together with the
          request 'remusr' to remove user features.