From: shaheed <sr...@ie...> - 2001-08-24 21:47:33
|
On Friday 24 August 2001 5:30 pm, Ian Leonard wrote: > It looks like it might be difficult to make a one-size-fits-all input > module. > Maybe it needs another plugin that can be used to determin network > and channel information. Or is having a plugin into a plugin getting > a bit silly. > > If the port and addresses can be determined via a standard network > protocol, fine. If not a config file of some sort (xml?) will be needed. I'm not arguing for a single input module for all networks. I am arguing for an API that will let multiple networks be supported. OVS does this by specifying addresses using strings of the form: protocol:info e.g. UDP:1.2.3.4:4000 DVB-ASI:1:2 AAL5-PVC:... AAL5-SVC:... which in API terms corresponds to a tagged union of all possible address types. Even if you don't agree on the non UDP address support, we ought to make something that can accomodate IPV6 as well as IPV4 addresses! Once we do that, we may as well allow an extensible scheme. |