- edited description
FetchTasks
"can we stop completely that task in 0.2.0 ? if needed we will re introduce it in 0.2.0.5 UI"
The problem the fetcher tasks are supposed to solve:
- bundle query related tasks in one place. currently whenever some data is needed it is directly queried from the remote resource
- prepare for stream based system, which also include a more event-driven strategy code
For UI what is needed is able to query the system and get results, without modifying the behaviour. Currently data is related to fetching/triggering it (getOrders => query remote exchange, wait for feedback, set variable).
Comments (14)
-
reporter -
reporter - changed milestone to 0.2.0.5 - UI
- edited description
-
reporter - edited description
-
Is the task still running in 0.2.0? Since we are not using it and there is no UI, with that out of the way simplify my testing of funcitonalities
-
reporter it's removed for 0.2.0.
for UI some getData function will be needed, i.e. getting data without changing the nubot (just observing).
-
reporter -
assigned issue to
-
assigned issue to
-
reporter - marked as critical
-
reporter implementation example see the 359 branch: https://bitbucket.org/JordanLeePeershares/nubottrading/branch/feature/359_store
-
reporter - changed milestone to 0.2.2 - Configurable Distribution
-
reporter - changed milestone to 0.2.1 - Liquidity distribution model
-
reporter - changed status to resolved
-
- changed milestone to 0.3.1 - Liquidity distribution model
-
- changed milestone to 0.3.3 - Liquidity distribution model
-
- changed milestone to 0.3.2 - Liquidity distribution model (t2)
- Log in to comment