255
edits
Drumbeat/Batucada/Future: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
In order to make requests to the CRM API in a way that does not affect the performance of the site (and hence the user experience), the integration will need to be asynchronous. We could use Django post_save signals on the models to send messages to a message queue. Another application could then consume tasks from the message queue and do the necessary work on the CRM side. | In order to make requests to the CRM API in a way that does not affect the performance of the site (and hence the user experience), the integration will need to be asynchronous. We could use Django post_save signals on the models to send messages to a message queue. Another application could then consume tasks from the message queue and do the necessary work on the CRM side. | ||
== Federated Social Web === | |||
* Drumbeat user accounts should be valid WebFinger identifiers (i.e. paul@drumbeat.org) and should resolve to an XRD with information about services used by the user. | |||
* Drumbeat should implement [http://ostatus.org OStatus] in order to support cross site follows / messaging. | |||
* We should aim to pass [http://federatedsocialweb.net/wiki/SWAT0 SWAT0]. The first "Social web acid test". | |||