SMP is a server. Well, so is SSP, but never mind that. Regardless if you are on SMP or SSP, there will still be lag.
There is no point doing the cable-batbox technique because packets will be reimplemented eventually. The reason they got rid of it was so they could optimize the E-Net. You still can't avoid resistance though, because resistance will be per block, but not per n-blocks, and will scale depending on cable packet tolerance.
( ramble warning questions/thoughts put down as they came to me)
your right it is a server for SMP just saying i am not worried about lagging caused by that..
Question then, will there be a config option to allow people to use cables longer if they wish?
I don't mind the function of loss after X blocks ( if there is a config so i can get it to feel "right" to me i will be happy ) but i would like to think with such a setting someone could say use HV cables rather the glass fibre..
Or have a option where HV can go a long distance but requires refreshing IE some new block or 2 transformers to keep it going with less loss?
reguardless your right there should be loss on cables do to leangth ( real world resistance) i feel that some cables being good for only one block is silly and the only multi block one is insanely expensive to run any distance
in the real world most appliances are DC volatage since its most effeiciant locally and they transmit long distances using AC current over a diffrent wire but using massivly increased voltage which helps overcome alot of resistance...
I would say long runs could go transformer to transformer and have X loss in transformers to convert ( a cost to run a long distance ) but have HV cables be the main wire between those!
IE HV wire wont hook up to anything BUT transformers or if you tried the packet/power would blow anything up without question! ( exception would be power generation blocks they would be able to add to the charge and not be shorted out? maybe?)
you would use copper or tin for local transformation!