GoodbyeFTP would be a lot easier to use if the user only had to remember
a URL, not an IP address.
Since most users will have a Dynamic IP, you should partner with a
dynamic DNS provider (such as DynDNS or TZO) to set up a link that
allows the user to easily create a dynamic DNS account. This should
probably be a feature in the server.
The server could even act as a dynamic DNS client to keep it updated.
TZO has really good developer support and offers a client that can be
modified to work with your software. DynDNS is a little less helpful,
but there are plenty of open source clients available.
Some things to keep in mind for the client:
1) It needs to get the WAN IP address and send that to the dynamic DNS
server (TZO has a URL you can use)
2) It should cache the WAN address, then periodically check to see if
the WAN address has changed. If so, it should update. If not, it should
do nothing.
3) TZO has additional requirements for a "well behaved" client,
available on their developer site
--
Troy
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Great idea.
I added to the PP.
Meanwhile, starting with build 1001, the system periodically looks up its WAN IP address via the TZO echo service, and show it on the main layout header.
Last edit: Sal Ingrilli 2012-11-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
GoodbyeFTP would be a lot easier to use if the user only had to remember
a URL, not an IP address.
Since most users will have a Dynamic IP, you should partner with a
dynamic DNS provider (such as DynDNS or TZO) to set up a link that
allows the user to easily create a dynamic DNS account. This should
probably be a feature in the server.
The server could even act as a dynamic DNS client to keep it updated.
TZO has really good developer support and offers a client that can be
modified to work with your software. DynDNS is a little less helpful,
but there are plenty of open source clients available.
Some things to keep in mind for the client:
1) It needs to get the WAN IP address and send that to the dynamic DNS
server (TZO has a URL you can use)
2) It should cache the WAN address, then periodically check to see if
the WAN address has changed. If so, it should update. If not, it should
do nothing.
3) TZO has additional requirements for a "well behaved" client,
available on their developer site
--
Troy
Great idea.
I added to the PP.
Meanwhile, starting with build 1001, the system periodically looks up its WAN IP address via the TZO echo service, and show it on the main layout header.
Last edit: Sal Ingrilli 2012-11-25
Here's more information on this (which you probably already have):
http://dyn.com/support/developers/