... | ... | @@ -20,6 +20,8 @@ We may want to restructure our abstractions, such as: |
|
|
|
|
|
We may want to stick with our current abstractions for the first round of re-architecture, since we know that models works. We could then focus on getting the queue/engine implementation sorted out.
|
|
|
|
|
|
That is, we can keep a known workflow and terminology, while still reaping the benefits of decoupling components, removing our dependence on Drush as a framework, etc. This latter on is our most pressing priority.
|
|
|
|
|
|
## Queue system
|
|
|
|
|
|
The queue is implemented using Celery, a full-featured task queue written in Python. The queue client should probably, by default, run locally to the web UI, so that they can communicate using a port on localhost.
|
... | ... | |