in defence of il, and more generally the idea that tcp is not the answer to every question, i have three points and one question:
1. i think this is one-size-fits-all thinking. tcp may be all things to all people, but i can't imagine that it's always the best solution. two new protocols were added to linux this year. if they thought "cisco doesn't support it, lets give up" they wouldn't have written 27kloc for sctp. (btw, there are a couple of commercial routers based on linux these days so sctp is probablly fairly routable.) 2. who said every project has to be the best use of one's time? and if that were really the measure, wouldn't we all be using windows? 3. and in this case, all protocols don't need to be routed. (unless somebody made a new rule.) perhaps that's an advantage if you want to keep your venti store to yourself. okay. so it's not routable over the internet, which may or may not be moot. are there any other reasons that il is no good? on my 1GHz pIV linux box, the tcp throughput test to one of my plan 9 machines (just to confirm some previously observed wierd performance numbers), linux was gasping for breath at 315Mbit with tcp. i'd really love to know how linux would fair with other protocols. - erik On Tue Sep 26 20:09:00 CDT 2006, [EMAIL PROTECTED] wrote: > the problem is firewalls and nat do care, and they are everywhere. > > back when i was purchasing large volumes of cisco equipment each year > for an employer, i tried to get cisco to add IL support to IOS. no > dice. apparently, we weren't purchasing enough. > > i agree with russ and jmk. IL is long dead. there are plenty of other > projects that would be a better use of your time.
