Re: shorten time to attempt to connect to back end
- From: "David W. Fenton" <dXXXfenton@xxxxxxxxxxxxxxxx>
- Date: Wed, 14 Sep 2005 12:49:55 -0500
"Danny J. Lesandrini" <dlesandrini@xxxxxxxxxxx> wrote in
news:f6GdnWS1RMlM0rXeRVn-hQ@xxxxxxxxxxx:
> Implementing it the first time isn't trivial. I'd have to get you
> the ASP code and the database, though what you see in the DBJ
> article is what I used as a basis.
???
Is it not the case that the web server could be written in any
server-side scripting language? I didn't read your code carefully
once I saw that it was dependent on IE (which makes it useless for
anyone concerned with producing robust and secure applications), but
you're just passing a call to a remote script on a publicly
available web server. The script on that web server could be ASP,
PHP, ColdFusion, Perle or whatever.
I'm not sure why the dependency on IE is needed. I long ago
implemented an upload function in an Access application that ran an
FTP script to upload data, and then called a CGI script on that web
server to process the files. I just used the default web browser (no
browser-specific dependencies).
For posting a single error message (as opposed to processing a group
of tab-delimited data files), one could skip the FTP and pass values
to the web script. The only difference is that your solution is
quite, whereas mine pops up a web browser window.
I think that if I were implementing this, I'd use the same FTP plus
executing the URL to call the script. The FTP would create a text
file with the error report. The URL would process that text file. I
think I'd implement the web-side application to poll the FTP drop
folder periodically, and give the user the option of reporting
immediately. If they choose not to, the message will be reported
within the interval I've chosen for polling.
That would remove any dependency on IE.
Of course, there's the firewall issue that you say your app solves.
I'm not sure how or why, because it defeats the purpose of having a
firewall. I think I'd set up a local proxy server in order to allow
users to communicate with a web app.
Interesing ideas.
Too bad you chose the Microsoft-dependent route for implementing it.
--
David W. Fenton http://www.bway.net/~dfenton
dfenton at bway dot net http://www.bway.net/~dfassoc
.
- References:
- shorten time to attempt to connect to back end
- From: Mike MacSween
- Re: shorten time to attempt to connect to back end
- From: Danny J. Lesandrini
- Re: shorten time to attempt to connect to back end
- From: Mike MacSween
- Re: shorten time to attempt to connect to back end
- From: Danny J. Lesandrini
- shorten time to attempt to connect to back end
- Prev by Date: Re: shorten time to attempt to connect to back end
- Next by Date: Re: I wish to rebuild all A97 tables from scratch - whew! Prefer to automate task.
- Previous by thread: Re: code for ASP Client Error Log
- Next by thread: Re: shorten time to attempt to connect to back end
- Index(es):
Relevant Pages
|