javascript - If todo functionality and chat functionality are in the same page, how to organize the structure? -
in flux architecture, how manage store lifecycle?
in flux app there should 1 dispatcher. data flows through central hub. having singleton dispatcher allows manage stores.
the chat example made facebook has 3 stores. there dependancies between each other, 'waitfor' others, still on same level.
if there todo functionality on page, add todo store same dispatcher, let @ same level chat stores? looks mess me.
how handle problem?
if there todo functionality on page, add todo store same dispatcher, let @ same level chat stores?
yeah, that's main idea. main idea of flux ideology there unidirectional flow going through 1 , single dispatcher. way can guarantee there cascading updates , happens strictly sequentially.
why think having dispatch action through different dispatchers make things easier?
Comments
Post a Comment