No subject

designed to ensure that a harvest source couldn&#39;t be harvested more<br>
than once simultaneously and get confused. Since the harvest job<br>
becomes multiple gathers and further split into fetches, James was<br>
keen to make sure a source could only have one job for each run of the<br>
cron. BUT I&#39;m sure we could get the backend (Redis if not RabbitMQ) to<=
br>
tell us the status of the job (and its related gather/fetches) and<br>
stop further ones being created until it is done.<br>
<br>
Would the various CKAN sites using the harvester (OKF, Frauenhofer,<br>
Canada, Washington etc.) be happy about this change? It would be on<br>
the CKAN 2.x code.<br>
<br>
Dave<br>
<br>
_______________________________________________<br>
ckan-dev mailing list<br>
<a href=3D"mailto:ckan-dev at lists.okfn.org">ckan-dev at lists.okfn.org</a><br>
<a href=3D"http://lists.okfn.org/mailman/listinfo/ckan-dev" target=3D"_blan=
k">http://lists.okfn.org/mailman/listinfo/ckan-dev</a><br>
Unsubscribe: <a href=3D"http://lists.okfn.org/mailman/options/ckan-dev" tar=
get=3D"_blank">http://lists.okfn.org/mailman/options/ckan-dev</a><br>
</blockquote></div><br></div>

--f46d043c826227e0c804e2b9df6a--