My experience is contrary to yours. Generally, I have Odin running through the day, and ZT most of the time. Over the last month at the least, ZT will disconnect but not Odin.
This perhaps needs to be broken down further. A disconnect typically implies that the IP has changed, and is different from a connection that has stalled for a few seconds and then starts functioning again. In case of a disconnect, Odin market watch will close (terrible behavior) and you can relogin again without closing the program. In ZT's case, the INT light will go red and there is no option but to close the program (via the program crash mode), and restart it.
There are two streams that are functional -- the broadcast/multicast mode that gets the quotes, and the unicast mode that caters to orders/trades. In the case of a connection stalling, I find that ZT's INT light (presumably the unicast mode) will sometimes go red. Here, it seems that Odin has better handling and larger number of retries, or rather more TCP-like behavior, as this rarely occurs. The 'Reconcile' action of ZT, unheard of to users of Odin, is possibly evidence of this.
The image illustrates a NOW unicast dropped connection. Odin was started before Now. After the internet occurrence, both recovered their broadcasts. But you could not operate NOW except watch quote updates in the market watch.
Both terminals have similar response behavior to broadcasts and, in case of the net stalling, have a refresh broadcast mode. One thing I wish ZT had is a mode to manually stop broadcasts. Data card and bandwidth conscious users would like such a feature that Odin has, specially when taking a tea break.
While ZT has its winning features, in the area of net handling it does not come near Odin. All said and done, this is an opinion; YMMV. Perhaps one of these days, I will fire-up WireShark and look more closely.
This perhaps needs to be broken down further. A disconnect typically implies that the IP has changed, and is different from a connection that has stalled for a few seconds and then starts functioning again. In case of a disconnect, Odin market watch will close (terrible behavior) and you can relogin again without closing the program. In ZT's case, the INT light will go red and there is no option but to close the program (via the program crash mode), and restart it.
There are two streams that are functional -- the broadcast/multicast mode that gets the quotes, and the unicast mode that caters to orders/trades. In the case of a connection stalling, I find that ZT's INT light (presumably the unicast mode) will sometimes go red. Here, it seems that Odin has better handling and larger number of retries, or rather more TCP-like behavior, as this rarely occurs. The 'Reconcile' action of ZT, unheard of to users of Odin, is possibly evidence of this.
The image illustrates a NOW unicast dropped connection. Odin was started before Now. After the internet occurrence, both recovered their broadcasts. But you could not operate NOW except watch quote updates in the market watch.
Both terminals have similar response behavior to broadcasts and, in case of the net stalling, have a refresh broadcast mode. One thing I wish ZT had is a mode to manually stop broadcasts. Data card and bandwidth conscious users would like such a feature that Odin has, specially when taking a tea break.
While ZT has its winning features, in the area of net handling it does not come near Odin. All said and done, this is an opinion; YMMV. Perhaps one of these days, I will fire-up WireShark and look more closely.
Last edited:
