| 63 | ==== (9/9): ==== |
| 64 | The primary steps of concern seem to be the following: |
| 65 | |
| 66 | 1. create a controller that can connect to other controllers |
| 67 | 1. pass messages between them (get one to send something to other) |
| 68 | 1. intercept and use messages (get recipient to act on message) |
| 69 | 1. make this symmetric (for request/reply/update) |
| 70 | |
| 71 | somewhere along the way, we need to devise a service type message/servicetype codes that can be meaningful. For now it is probably a good sanity test to get two controllers to connect to each other, akin to what !FlowVisor does. |
| 72 | |
| 73 | The easiest approach may be to create a module that opens up its own connection, exporting a "switch service" that handshakes with a remote controller. |
| 74 | |
| 75 | |