Chronotope’s avatarChronotope’s Twitter Archive—№ 56,230

          1. …in reply to @mbseid
            mbseid Well, proxies mby, but async ones, which is sort of the whole point. By handling requests outside of the execution chain, true async
            Permalink On twitter.com Twitter logo Chronotope’s avatar Mood +2 🙂
        1. …in reply to @Chronotope
          mbseid For ex, a Store can stand as an async gateway to an API. But it can also be used to manipulate statefulness on img load w/o blocking
          Permalink On twitter.com Twitter logo Chronotope’s avatar Mood -1 🙁
      1. …in reply to @Chronotope
        mbseid So I can load tiny images, emit their URLs to a store, wait until my master component has mounted, then emit actions to load...
        Permalink On twitter.com Twitter logo Chronotope’s avatar Mood 0
    1. …in reply to @Chronotope
      mbseid ... Img() in the background, and update the Store on completion. That then updates component state with larger images. ...
      Permalink On twitter.com Twitter logo Chronotope’s avatar Mood 0
  1. …in reply to @Chronotope
    mbseid By manipulating the Store to alter component State, I control HTTP requests, and run it w/o blocking unrelated components.
    On twitter.com Twitter logo Chronotope’s avatar Mood -2 🙁

Search tweets' text