Quote:
|
Originally Posted by Len
I apologise for the inconvenience but I have moved these post from another thread as it would be a shame to lose the good information.
If software and severs were in perfect working order we would still experience the odd glitch. The data that’s being passed backwards and forwards could be corrupted by perhaps noise or the odd spick from the wiring or sumat. There are probably millions of devices/machines out there that generate interference that all could potentially interfere with the data that’s passing by. But then that’s the internet for you. It’s probably never gong to be perfect.
|
thats why TCP has inbuilt error tracking. There will never be an item of data that is 'interfered with' that is accepted at the receiving end. There is a cracking video of how 'stuff' makes its way round the net here
http://www.warriorsofthe.net/movie.html
be warned its BIG (73 Meg) but its a) very funny and b) very informative.
Also when it comes to databases updates, the industry standard is to use a 2 phase commit process to ensure nothing becomes corrupt. I'm not sure if vBulletin uses this yet or even what DB is hanging off the back end(MySQL if I was pressed to guess??)