Right now it's redundant (everything in SBServer calls it, could call directly) and probably creating cycles. One idea is to turn SBClientController into an Operation that handles the argument building and HTTP lifecycle, including timers. This would make it observable in the UI.
Right now it's redundant (everything in SBServer calls it, could call directly) and probably creating cycles. One idea is to turn SBClientController into an Operation that handles the argument building and HTTP lifecycle, including timers. This would make it observable in the UI.