http://localhost/ticket/1019 <p> We propose the following push approach using individual packages: </p> <ol><li>New, updated and deleted packages are pushed to a url endpoint on Wordpress (WPURL). This endpoint will be a configuration option on the CKAN side. A POST or PUT http method will get used. The payload will be a json document of the following form: </li></ol><blockquote> <p> { </p> <blockquote> <p> payload: The entity data as available from the REST API entity-type: 'Package', operation-type: 'create'|'update'|'delete' # one of these options </p> </blockquote> <p> } </p> </blockquote> <p> It will be sent as the body of the request with content-type set to application/json. </p> <ol start="2"><li>The wordpress side will provide a 200 on success. Any other response will be taken as a failure. On failure, submission will be archived and failure logged and notified to system administrator. Submission can be resent later automatically by sysadmin after review. </li></ol><ol start="3"><li>Pushes will happen continuously and approximately simultaneously with updates (a webhooks type model) </li></ol><ol start="4"><li>[optional] CKAN side will support configuring authorization for basic authentication if applied on WP side. </li></ol><ol start="5"><li>[optional] List queue status (including failures) on ckan adminstrative dashboard. </li></ol> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1019 Trac 0.12.3 pudo Thu, 03 Mar 2011 15:42:10 GMT http://localhost/ticket/1019#comment:1 http://localhost/ticket/1019#comment:1 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> </ul> <p> fixed in <a class="ext-link" href="https://bitbucket.org/okfn/ckanext-webhooks/changeset/034647931921"><span class="icon">​</span>https://bitbucket.org/okfn/ckanext-webhooks/changeset/034647931921</a> </p> Ticket