...
At the moment, a Jetty thread blocks whilst long running operations are in flight.
As a user, I would want to be able to monitor a long running operation and know its result, even if I logged off and returned later. We might consider making long running tasks cancellable too.
Maturing the REST API
Swagger
Use of range header
Backward compatibility.
Default depth / including children in the JSON
Omitting fields on update
Prevent Deletion of the objects that are in use
(QPID-7197)
At the moment we have repetitive code scatter throughout the implementation that verifies that an object that is about to be deleted is not in use. We want to shift this responsibility to the core model. There are a couple of options, one it outline on the Jira,