On 08/29/2014 12:26 AM, Royce Lv wrote:
Problems to solve:
When we generate the debug reports (or upload/download a storage volume), only the request initiator gets task id, and is able to query task status. We need other users from other browser to have same view as the initiator, which is not possible now.
Solution: 1. We add async event information, events will also be classified so that users can subscribe events interest them
2. We enable reverse mapping (task to resource which generate them) query for users. So that user can find tasks related to a collection: GET /tasks?init_collection=debugreports after take a look at current implementation, we can also query taget_uri GET /tasks?target_uri=r(^/debugreports/*) (need to be encoded)
Good explanation, Royce! I think we can use /tasks?target_uri=<uri-pattern> to do that. So when loading the UI, we query for the resources to properly display them while they are being generated. I think it is simple to do that now. I also can help coding.
Since we currently out of support of async events, we may want to add task query for this purpose.
Welcome comments!