I contemplate creating a real-time application when iPod Touch / iPhone / iPad talks to a server component (which produces MIDI and sends it further to the host). When I ping iPod Touch on Wi-Fi, I get a huge delay (and a huge dispersion too):
64 bytes from 192.168.1.3: icmp_seq=9 ttl=64 time=38.616 ms
64 bytes from 192.168.1.3: icmp_seq=10 ttl=64 time=61.795 ms
64 bytes from 192.168.1.3: icmp_seq=11 ttl=64 time=85.162 ms
64 bytes from 192.168.1.3: icmp_seq=12 ttl=64 time=109.956 ms
64 bytes from 192.168.1.3: icmp_seq=13 ttl=64 time=31.452 ms
64 bytes from 192.168.1.3: icmp_seq=14 ttl=64 time=55.187 ms
64 bytes from 192.168.1.3: icmp_seq=15 ttl=64 time=78.531 ms
64 bytes from 192.168.1.3: icmp_seq=16 ttl=64 time=102.342 ms
64 bytes from 192.168.1.3: icmp_seq=17 ttl=64 time=25.249 ms
Even if it is twice as much as the iPhone-> Host or Host-> iPhone will be, 15 ms + is too long for the application that I am considering. Is there a faster way to do this (like a USB cable)? If not, will the Android app build any other options?
Traceroute reports more working times:
traceroute to 192.168.1.3 (192.168.1.3), 64 hops max, 52 byte packets
1 192.168.1.3 (192.168.1.3) 4.662 ms 3.182 ms 3.034 ms
- ping traceroute , , ( ) ?