Bug List

Page Networking Scheduler API
State variables aren't working in SSocket Since SSocket doesn't keep any information of it's own, and calls to implementation are passed through Request engine, queries on socket state right after issuing a function, e.g. connect() on it, return wrong state, since the call hasn't been passed to implementation yet. Possible fixes include setState method in implementation classes, or an additional state variable in SSocket class (latter is prefered).