Re: How to prevent 404 error when a page is updated via ftp?

From: Robm (robm_at_rkmengineering.com)
Date: 03/09/04 

Date: Tue, 9 Mar 2004 15:08:28 -0500

Jim, the data is 1-minute averages and hourly average values for about 10
parameters in an air quality monitoring application. So the source data
updates once a minute. The data server formats this data in a single html
file and uses ftp to send it to the web server, also once a minute. The page
autorefreshes so that the user can just have the page open and see the most
current data at all times.

I am now working on a scheme where the ftp-ed files are read by a separate
process which places the data in tables of an MS-Access database. This
database is then used by the Visual Interdev website to display the data. So
I am using the original Visual Interdev web design but I am replacing the
direct database links between data server and web server by ftp-ed files. I
haven't completed this yet, but I believe that it should work fine.

Rob M

"Jim Buyens" <news@interlacken.com> wrote in message
news:36a7e008.0403082003.2efa3596@posting.google.com...
> Can you describe the application a little more? For example:
>
> o What kind of data is this?
> o How often do updates occur?
> o When updates occurs, how many files are affected?
> o Are the updated files HTML, GIF, JPEG, or what?
> o Why do the Web pages need to auto-refresh every 60 seconds?
>
> Jim Buyens
> Microsoft FrontPage MVP
> http://www.interlacken.com
> Author of:
> *----------------------------------------------------
> |\---------------------------------------------------
> || Microsoft Office FrontPage 2003 Inside Out
> ||---------------------------------------------------
> || Web Database Development Step by Step .NET Edition
> || Microsoft FrontPage Version 2002 Inside Out
> || Faster Smarter Beginning Programming
> || (All from Microsoft Press)
> |/---------------------------------------------------
> *---------------------------------------------------
>
>
> "Robm" <robm@rkmengineering.com> wrote in message
news:<jx23c.2783$j05.146579@news20.bellglobal.com>...
> > Jim, regarding your question "How did the database connection play into
> > this? Were you putting the automatically-updated content in a
database?":
> >
> > In the original design there an MS-Access database resided on the web
> > server, and the web site simply filled tables from that database, as
> > requested by the users. The data server, on the other side of the
firewall,
> > would use temprary mapping and a database link to place new records in
the
> > tables of the web server's database. This worked fine with one customer,
who
> > wanted it this way.
> >
> > The new design, for a customer who does not allow temporary drive
mapping,
> > is much more restrictive, in that we only have fixed pages with data.
These
> > pages are prepared in html format on the data server, and are then
ftp-ed to
> > the web server. The problem, as reportes in this thread, is that the
files
> > get locked up for considerable time, possibly due to virus checking,
> > possibly die to the server deciding to keep them locked, two suggestions
> > supplied by others in this thread.
> >
> > I have no experience with ASP.NET and am worried about the learning
curve. I
> > have lots of Visual Interdev ASP experience, and could use that for
sure.
> > Thanks for the suggestions!
> >
> > Rob M.
> >
> >
> > "Jim Buyens" <news@interlacken.com> wrote in message
> > news:36a7e008.0403080939.4b3533a@posting.google.com...
> > > "Robm" <robm@rkmengineering.com> wrote in message
> > news:<J8L2c.903$hG.50458@news20.bellglobal.com>...
> > > > Thanks. I already tried to reduce the time by ftp-ing to a .tmp file
and
> > > > then removing the original and renaming the .tmp file. Even so I
find
> > that
> > > > the page is unavailable for too long a time. I had this working
> > originally
> > > > as a Visual Interdev web site, with a database connection to the
data
> > > > server, but my customer doesn't allow this any more. Why would the
page
> > be
> > > > unavailable for such a long time (multiples of tens of seconds)? The
> > file
> > > > size is under 4K!
> > >
> > > Sometimes IIS holds files open, to save time reopening them if
> > > additional requests arrive.
> > >
> > > This would lead me toward the solution of having an ASP or ASP.NET
> > > page open and transmit the automatically-updated file, rather than
> > > letting IIS deliver it directly. That way, you have more control over
> > > file opening and closing.
> > >
> > > How did the database connection play into this? Were you putting the
> > > automatically-updated content in a database?
> > >
> > > Jim Buyens
> > > Microsoft FrontPage MVP
> > > http://www.interlacken.com
> > > Author of:
> > > *----------------------------------------------------
> > > |\---------------------------------------------------
> > > || Microsoft Office FrontPage 2003 Inside Out
> > > ||---------------------------------------------------
> > > || Web Database Development Step by Step .NET Edition
> > > || Microsoft FrontPage Version 2002 Inside Out
> > > || Faster Smarter Beginning Programming
> > > || (All from Microsoft Press)
> > > |/---------------------------------------------------
> > > *----------------------------------------------------

Loading