start work on modular network interface
We need another layer of network API to sit atop the simplenet/torus/dragonfly components.
Some notes from a previous discussion on this topic:
- some key points: - we need for some components to use multiple transports ( like an ion talking to both compute and storage network ) - we have the event to be delivered to remote lp, and event to be delivered to self once local completion is done _forward() msg _self() msg - each network method can implement a set of function pointers to populate a struct. The top level API will just map each call to the right function pointers - API name: model_net_*** - this API stuff doesn't address how to initialize the right LPs for your configuration, or where to put those LPs - this feeds into the LP mapping configuration problem