Hi-
You might also want to look into https protocols and the like. The data is encrypted in the transmission. This is commonly used when doing web based credit card shopping.
Depending upon your server application program and your OS there are various levels of security that can be passed to it. I cannot answer for Windoze, nor any http server other than Apache, but for Linux and Apache, turning on sessions control and secure transmissions, might prove to be adequate for those not wishing very hot or very cold buildings or pumping into or out of unexpected situations.
One easy to implement "trick" is to have the http server "listen" on a non-standard 80 or 8080 port number. This will NOT help with the determined attacker but will help with the casual ones. But, it cuts down on the rif-raf and is easy to implement.
When dealing with slow transmissions, you might want to consider a Java applet for the communications. I'm not a big fan of Java, but passing along large amounts of data can be reduced by proper construction of the data packets between the server and client. This is when you want to have icons in the pages, and have them manipulated on the web page. Simple text and forms is another option, allbeit not as "pretty". If you have a limited set of icons you might get away with preloading them via Javascript and using those images. Another "trick" is to use "tables"
with different background colors and different widths of
the fields. This can generate a very quick horizontal bar graph without sending an icon (picture) at all. Very little overhead.
Please also note the terms and conditions of whatever DSL
service is available. I know in my area, SBC does NOT
allow one to host a web server. I had to go to a smaller
third party provider that uses SBC equipment to obtain
a lower cost option. Errrr, I should say that SBC did not
provide a "non-business" DSL connection. They do offer one
for significantly more $ per month.
I think that you can easily implement a dynamic DHCP
(unknown IP address) via some free services. One of the links that I have (that I HAVE NOT RESEARCHED NOR USED) is:
Again, I haven't used the service so I cannot comment on it.
You may or may not still want to select a domain name and registrar for your application. It is not necessarily a requirement. I am assuming that your audience is very limited (hopefully) and that you can get away with something like:
for getting to your pages. Heh, heh, the 192.168.1.1 is not a very valid number to use. It's a level C address that is commonly used for local access..... but you get
the idea.
Please keep us posted. I personally am very interetested in dynamic web insturmentation, and would like to hear of your progress.
Finally, for the rural pumping station. Might I suggest that you get your company to pay for DSL at your house, then have the server do a PPP to the pumping station. Having the server at your house is pretty easy. I have my server on top of my freezer in the garage. It acts as my mail server, web server, DNS, firewall and NAT. If you can get the company to pay for the DSL at your house, and the cost of a cheap PC, you might (hint, hint) be able to leverage the DSL for your own uses. After all it's a fair trade for the electricity that the server is using......
Then a dedicated phone line for the PPP link.
Hope these rather unconnected thoughts help.
Cheers,
Rich S.