Basically, it does nothing better than the navigator, except that you can define the maximum slippage you accept for one-click trading. There are charts, but its nothing to write home about (you cant even scroll or zoom).
Its web-based, and has a different look and feel. Same tendious order-entry for bracket-orders like in the navigator. You need like 5+ clicks to place a limit + bracket order. Obvious stuff like mouse-wheel or curser up/down for numeric input isnt working. Im not at all impressed by the design of the order-entry mask, usability-wise its not an improvement from the navigator.
Also, they said they would utilize the akamai network to minimize latency, but TCPview tells me its an good old 'normal' internet-route from here (europe) to phoenix, no akamai at all..
Well, they are different destinations. Not sure what I expected to see, but you prompted me to take a look:
The first is Remote Trader, then Navigator...
> tracert 8.10.179.197
Tracing route to 8.10.179.197 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 17 ms 8 ms 5 ms 1-72.96-97.tampabay.res.rr.com [97.96.72.1] 3 9 ms 8 ms 9 ms gig12-0-0-2527.tampfledc-rtr2.tampflrdc.rr.com [65.32.24.86] 4 10 ms 10 ms 11 ms ge2-2-0.tampfledc-rtr4.tampflrdc.rr.com [65.32.13.66] 5 9 ms 8 ms 8 ms te-3-1.car2.Tampa1.Level3.net [4.79.146.1] 6 36 ms 35 ms 35 ms ae-7-7.ebr1.Dallas1.Level3.net [4.69.133.42] 7 44 ms 39 ms 47 ms ae-61-61.csw1.Dallas1.Level3.net [4.69.136.122] 8 40 ms 40 ms 42 ms ge-0-3-0-69.bbr2.Dallas1.Level3.net [4.68.19.2] 9 99 ms 63 ms 158 ms as-1-0.mp2.Phoenix1.Level3.net [64.159.1.122] 10 62 ms 62 ms 63 ms ge-8-1.hsa1.Phoenix1.Level3.net [4.68.98.100] 11 64 ms 65 ms 72 ms 8.10.179.197 Trace complete.
>tracert 216.52.236.194
Tracing route to 216.52.236.194 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.1 2 8 ms 9 ms 6 ms 1-72.96-97.tampabay.res.rr.com [97.96.72.1] 3 8 ms 9 ms 9 ms gig12-0-0-2527.tampfledc-rtr2.tampflrdc.rr.com [65.32.24.86] 4 9 ms 8 ms 7 ms ge2-2-0.tampfledc-rtr4.tampflrdc.rr.com [65.32.13.66] 5 32 ms 44 ms 35 ms ge-2-1-0.cr0.dfw10.tbone.rr.com [66.109.6.106] 6 34 ms 34 ms 34 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179] 7 31 ms 33 ms 37 ms 66.109.9.214 8 70 ms 63 ms 64 ms INTERNAP.te1-4.ar4.LAX1.gblx.net [64.215.30.78] 9 74 ms 72 ms 68 ms border16.ge3-0-bbnet2.lax.pnap.net [216.52.255.84] 10 73 ms 73 ms 74 ms mbtrading-3.border16.lax.pnap.net [63.251.223.218] 11 75 ms 73 ms 73 ms 216.52.236.194 Trace complete.
AFAIK, those ips above are the order servers. I think only the quotes run through the akamai farms, so we're still dependent on the order servers on the US West Coast (I did this sort of investigation a while back, as latency is an issue for me (Australian-based)). If you want to see if you're using an akamai farm, when trading is open:
Start > Run.
"cmd" + Enter - command prompt opens.
type: "netstat -a" + Enter
this lists all the current and past connections over any network interface on your PC (to local servers on your network and the internet etc) - look for akamai connections there.
I've seen them in there - and I'm only using Navigator (demo).
I was using TCPview(which does simmilar stuff like netstat, amogst other things) from the SysInternals suite while RemoteTrader was running, and there were only 2 trading related connections open, no akamai tho. Both TCP sockets connected to machines directly in the USA, it appears to me that there is no special routing going on.
