Thanks for the write up Victor. It was an interesting read, though I won’t say I read very closely or critically.
I am interested in your views on a question about routing and how it’s currently accomplished. I’m putting the containers into a network metaphor so they can be viewed just as any network packet traversing the internet. Is the container routing similar in that regard where the “packet” hits various hops on the way and some mechanism exists for calculating the current best path to the end point?
It wasn’t clear to me from your post if there was anything like a defined path at the outset or what “next ship out” in the case of some container delay on the way meant next ship that was eventually going to the destination or next ship with the quickest expected delivery—or even if the information for making such an assessment was easily available.
Thanks for the write up Victor. It was an interesting read, though I won’t say I read very closely or critically.
I am interested in your views on a question about routing and how it’s currently accomplished. I’m putting the containers into a network metaphor so they can be viewed just as any network packet traversing the internet. Is the container routing similar in that regard where the “packet” hits various hops on the way and some mechanism exists for calculating the current best path to the end point?
It wasn’t clear to me from your post if there was anything like a defined path at the outset or what “next ship out” in the case of some container delay on the way meant next ship that was eventually going to the destination or next ship with the quickest expected delivery—or even if the information for making such an assessment was easily available.
It’s not like a network packet, there is a planned route from the outset. This route is also used to set the correct price to charge.
The path might be changed when logistically required (by delays, congestion, capacity limits along the routes), but this is infrequent.