On Mon, 2006-16-01 at 09:21 +0100, Willem de Bruijn wrote: > The reason I ended up with it was purely practical and > even grew out of a single-module system. Streams fitted our use-case, which > is to run code in userspace, kernelspace and on the network-card. > Communicating across 3 environments breaks function-calling as a viable > method -- e.g., from context-switching.
Ok, that does seem different and valuable. It seemed to me your motto was "flexibility first, performance next" thats why i suggested to use Java instead ;-> > (*) one problem with streams-like abstractions is that they don't fit the > real > world al that well. For example, IP and TCP handling cannot easily be > separated, since TCP needs to look at IP headers again. In extremis you end > up with 1 big functional module again. John: Have a look at the xKernel for > some pros and cons of streams. I forgot to mention that before. In the > meantime I'll read through the netfilter sourcecode :) > I dont think you need to look at the sources. You could look at examples and usage; look at tc filter/actions as well. cheers, jamal - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
