How to actually publish your application

[Keith]

Hi

Have built an application for the WWW which in itself has a simple interface.  It displays a Form with a number of tabs where data can be input and another tab where results are displayed.  But there are other things that must be added - documentation, links to get help, blurb about 'what's coming next' etc

We have secured a domain name and I wanted to know if the way to address all of these extras to create a standard web page with links to all of the information and an 'Enter' button to fire up the actual NT application (which is the way I am thinking about doing it now) or should it all be developed with NT?

Thanks for advice.

Keith

[Nick]

You can easily link from a "traditional" webpage to a NT-server.
If the NT_server is just meant to gather information from some people then this could be the way to do it.

Nick

[kevin plummer]

NT also serves up static pages very well. I pulled a webpage down that was hosted on iis and host internally via NT. I didn't need to make any changes to the website. I just took one of the NT examples and made the default page index.html and changed the port to 80. The website has never crashed.

I'm currently working on an app combining a static website with a web app + it allows me to easily add dynamic content and also access my DB files.

[Bruce]

Hi Keith,

>> We have secured a domain name and I wanted to know if the way to address all of these extras to create a standard web page with links to all of the information and an 'Enter' button to fire up the actual NT application

There are many ways to set this up - the answer becomes "pretty much any way you like".
Our Capesoft.Com site though is an example of a "mostly static" site mixed with some dynamic browses and forms.
the way I did that was as follows;

a) created all the static pages, as desired, and placed them in the web folder (and subfolders).
b) created dynamic browse and form procedures.
c) created links to the procedures on static pages where desired.

There's no need for another server.

Incidentally whichever way you do it, your web server is always running. So the phrase "fire up" is misleading. A better phase would be "link to". "Fire up" has connotations that the Exe starts, and stops, as users want to use it, and that is not the case.

cheers
Bruce

[Keith]

Thanks Nick, Kevin, Bruce

Good info (as usual) and lots to consider. 

Cheers

Keith