- Client will have own Action and Model
- Model is TODO but needs to hold all of the aborts
usually a front-end client wants to abort other ongoing requests
- Network.Client will have an update function that uses effectSub to
create a thread that will inform the app of the results of the xhr
action. We shouldn't just do this in Main, it gets messy
- There's a lot of wrong here:
- Send function is referenced from the GHCJS.DOM.JSFFI.Generated
directly, so idk if this compiles to native (it's fine to ignore this
point though because we only really care about the front-end for XHR)
- There are actions that should be generalized out, probably there
needs to be a network client component, with an interface to keep
track of stuff for us accross different actions that trigger http
towards-a-new-leftypol