<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
<font face="Arial">We now have a few calls that are executed
asynchronously and return 202 status with TaskStatus object,
instead of the actual entity. Some examples are:<br>
<br>
POST /api/repositories/:id/sync<br>
POST /api/providers/:id/sync<br>
<br>
I think we should acknowledge the fact that async tasks are a
resource on their own, and give them a dedicated url, something
like:<br>
<br>
POST /tasks/sync/provider/:id<br>
POST /tasks/sync/repository/:id<br>
<br>
to initiate a sync process.<br>
<br>
To get the status:<br>
<br>
GET /tasks/:id<br>
<br>
or perhaps we should be more specific:<br>
<br>
GET /tasks/sync/:id<br>
<br>
What do you think?<br>
-d<br>
<br>
<br>
</font>
</body>
</html>