hmDelete
hmDelete = 5
Example
procedure DeleteResource(Client: TvxHTTP; const URL: String);
begin
Client.Delete(URL);
end;
Usage
hmDelete selects an outbound HTTP DELETE request while the current Velox API runtime does not execute inbound DELETE.
Additional Technical Info
hmDelete is ordinal 5 of TvxHTTPMethod. TvxHTTP.Delete selects it and calls Indy's DELETE overload that captures response content.
Velox does not pass its staged Content stream to DELETE. Any previously loaded request content is ignored for dispatch and then cleared in finally. Put request selectors, identifiers or preconditions in the URL and headers according to the target API rather than assuming a DELETE body will be sent.
DELETE is idempotent in standard HTTP semantics but is not safe: it requests removal of an association/resource. Idempotency does not guarantee that repeated responses, audit events or asynchronous side effects are identical. Retry only when the endpoint contract, identifiers and failure evidence make it safe; use conditional fields where the API supports them.
Velox returns HTTP error status/content through Response rather than raising protocol-status exceptions, so check the result explicitly. Transport/setup failures can still raise. Generated OpenAPI maps this enum to DELETE, but the current inbound TvxRESTManager has no DELETE execution branch and does not enforce stored RESTMethod.
The example is source-reviewed only; no DELETE, API, network, runtime or image test ran.
Related Code Library entries
hmGet- safe retrieval.hmPut- idempotent representation update.TvxHTTP.Delete- outbound call.
External references
Created 2026-07-15