Comment Re:35? (Score 1) 376
Just FYI, when someone misspells things at the rate you do (it's "C'est la vie", "breach of contract", "</p>"), I'm not inclined to trust their memory regarding fine detail or attribute credibility to their interpretation of said fine detail.
You might want to introspect about that.
Of course, WTF kind of network admins don't understand about buffering effects on dataflows?
Last question first: those admins who haven't worked with large numbers of TCP-to-serial converters -- I'm talking 6,000 independent datastreams at the same time -- and forget how TCP buffers get filled from a 1000 cps steady-rate source when the converter calculates a RTT of 2 milliseconds over the local network between it and the server. A server running as a guest in VMWare, with no packet aggregation optimization in the host's Ethernet interface. Who never heard of the word "thrashing". Who never saw the guest's real-time clock losing time because of interrupt overload. Who never took a WireShark capture of a connection, to see just how many packets are created for each stream
Criticism on my English and my spelling from an Anonymous Coward? Like that's worth much. Yes, I misspelled some stuff, but that's because what I published was first draft done in a hurry. If it were an article for paid publication, I would have used a real word processor, with a real spell checker, instead of a stupid HTML form. (Free Republic, another forum I occasionally contribute to, does have a decent spell-checker in its contribution entry form.)
And I'll be the first to say that my memory is a photographic one, but the filmbase is made from Swiss Cheese. That's why when I design a system, I use a number of methodologies to minimize the dependence on memory. I tend to design from the top down, then revise from the bottom up. Repeat as needed to nail down the details. I also create use cases: "I'm x and I need to do y," and then I ensure each case is covered in the initial design specification. I'm also a great fan of concordance generators to identify and eliminate "overloading" variable names within a project. Ever hear of one?