Had a good meeting last night with some guys from a mobile
networking company. They would like to think they've solved
a latency problem with mobile TCP/IP.
Unfortunately, their attitude to their work was similar to
that relating to cryptographic algorithms.
Especially when I mentioned that there were a number
of RFCs specifically related to latency problems with "long
thin pipes" (long transmission time, not much bandwidth).
So, like the amateur guy with the brand new encryption
algorithm, they think they know better (which they may do),
but aren't prepared to release their "algorithm" for peer
review. (And not even prepared to release it to me - a
friendly consultant under NDA!).
They mainly want me to work out how to productise their
solution. Quite difficult when you don't know what it