Hi,
If you can use dyndns (your mobile interner provider allows direct incoming connections to the phone), then our server androidwebkey.com will redirect to your phone's ip address. So after a second it's the same.
Best wishes,
Peter
There are two cases:
- you are lucky: your phone can accept direct connection, because your
mobile interenet provider lets your phone to do that
- you are not lucky: your phone can't, or you are using wifi (which is
behind a NAT)
If your are lucky, then
- you can use DynDNS. For example entering yourPhone.homeip.net
redirects to your ip address, so your browser and your phone are
connected directly, while you can see yourPhone.hoemip.net in the
browser's address line
- you can use our server, which will redirect you to your phone's ip
address (we are talking about http redirection), for example to
1.2.3.4. Then the connection between your phone and the browser will
be direct, and you can see your phone's IP address in the address bar.
If you are not lucky, then
- DynDNS won't work at all
- our server will tunnel the connection, which means that both your
phone and your browser connect to our server, which replies the
packages to the other side.
I hope it helped.
Best wishes,
Peter
Yes, direct connection is always faster.
The fastest: using wifi at home
slower: direct mobile connection (not always possible)
slowest: using our tunnel (it always works, and redirects to the
direct connection if it's possible)
Best wishes,
Peter
Sure, you need. The dyndns resolves the name like
yourphone.homeip.net to an IP address, which belongs to your router.
Best wishes,
Peter