it would probably be good to separate host and browser based connections in network.js. since these are different environments in terms of security resource, not all things will be the same.
so there would exist separate namespace to networkhost.js and networkbrowser.js. code that is shared could still be in network.
abstract the connection usable by clients and servers ("protocol")
it would probably be good to separate host and browser based connections in network.js. since these are different environments in terms of security resource, not all things will be the same.
so there would exist separate namespace to networkhost.js and networkbrowser.js. code that is shared could still be in network.
abstract the connection usable by clients and servers ("protocol")