Re: how to put an app on the web

From: Brion L. Webster (brion.webster_at_nospam.ci.fresno.ca.us)
Date: 03/18/05


Date: 18 Mar 2005 08:26:22 -0800

Jon Purvis wrote:

Most of my apps are D7/ADO/Access (or D7/ADO/<big SQL database>),
and I've dabbled with getting some of them to the Internet.

There are two main ways of making "internet" applications - ones
that use the internet as a transport protocol, and ones that
program the browser.

My experience with users is the data entry ones loathe browser
apps, given any other choice, while the management ones love them.
Browsers tend to be keyboard unfriendly, especially with tab
orders. So depending on how your users drive your app, they may be
really put off by clicking and typing and clicking.

Making Active Forms out of things hasn't worked very well for me,
but that might be more about my programming skills than anything
else. One huge drawback is it will limit you to Internet Explorer
as your browser. Granted, you're already tied to Windows
(presumably because you're using Delphi), but do you really want to
lock yourself out of FireFox?

My most stable "internet" applications are rich Win32 clients that
use TCP/IP to get to a middle tier server, that then writes back to
a database. As someone else pointed out, ASTA is a perfect
enabler. You basically switch out all your TADOxxx for TAstaXXX,
write a little database resolver, and go. ASTA even automatically
updates clients when a new version is released, you check the new
release onto the server, when a client connects ASTA compares
version numbers, and silently updates the client. You don't say
what version of Delphi you're using, MIDAS/datasnap may be the
cheaper way to go if you've got Enterprise.

This gives you the benefit of a rich Win32 user interface, possibly
even exactly the same one you're using now. You've got full
keyboard support, tab order control, etc. It takes virtually no
bandwidth (except if you're updating clients - that can be painful
on dial-up). It also gives you a fairly easy way to change
databases - just release a different resolver. You can configure
the server side and the client side to talk wherever it needs to go.

As for browser-programming...I'd highly encourage you to look at
IntraWeb. It beats the pants off of WebSnap and WebBroker (the
other "Delphi native" web frameworks). You can either write an
isapi dll (requires IIS hosting) with D7 Pro, or a fully standalone
web server with D7 Ent+. http://myserver.tx.us:9999 would bypass
IIS (and all it's administrative nightmares) and go right to your
intraweb app. IntraWeb would then serve pages back to the browser.
The browser "interface" is so very different than a Win32 interface
that I really doubt the same UI design would work.

-Brion



Relevant Pages

  • Re: ISA Server Problems, please help
    ... > clients are unaffected, is it secureNAT clients which are affected? ... then checked Send the original host header to the publishing server instead ... > provided unrestricted internet access. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server Problems, please help
    ... Based on the rules you have listed, SecureNAT clients should only be allowed ... The All access rule for SBS Internet Users ... Web Proxy and/or Firewall Client ... > header to the publishing server instead of the actual one. ...
    (microsoft.public.windows.server.sbs)
  • Re: After installing SBS 2003 two IE 6.0.29 SP2 clients that cannot to companyweb
    ... Mozilla, and other clients can access the http://comanyweb, the SBS server ... Reset the Internet Explorer Settings to Default. ... DHCP was turned off in SBS 2003. ...
    (microsoft.public.windows.server.sbs)
  • Re: Firewall Beginners Assistance
    ... make primary internet access on port 8081 ... clients could update the browser using .pac files ... DNS - so, it might be wise to use it anyway. ... why owning a DNS server?? ...
    (comp.security.firewalls)
  • Re: Clients cant browse the web after apply SBS2K3 SP1
    ... different issue and solutions and this newsgroup is for English version ... we must check if the DNS server works properly. ... >Subject: Re: Clients can't browse the web after apply SBS2K3 SP1 ... The error is "Internet explorer can't open the search page". ...
    (microsoft.public.windows.server.sbs)

Loading