I know that my Reflection 1 v5.2, at least, has a transfer setup
option to turn a <CR/LF>
into a record separator (and vice-versa on a download). However, to
my knowledge, it
does not have an option to set any other character combination to do
this-only to turn this
translation on or off. The only other thing I would know to do is to
provide your users with a
script to upload the file using a set fixed format. I am about to
write a 'button' for my users
to use with a new app here to insure that some PC data files are
uploaded with a 'proper'
MPE name and the proper file attributes.
--
Rick Brooks
Database Systems Legacy Team Leader
Prevue Networks, Inc.
[log in to unmask]
See what's on! www.prevue.com
-----Original Message-----
From: Stan Sieler [SMTP:[log in to unmask]]
Sent: Wednesday, September 17, 1997 4:29 PM
To: [log in to unmask]
Subject: Web vs DOS vs WRQ
Hi,
I'm looking for suggestions for solving a problem in downloading
(from a 3000, via web), uploading (to a 3000, usually
via Reflection), and streaming.
We have a large text file (a 1 MB STREAM file) on our HP 3000,
which we want to be able to have people download to
their local machine via a web browser.
The resulting file will then be uploaded to a second HP 3000,
where it will be STREAMed.
The problem is that we realize that most users will download to
a PC ... and both Netscape and MSIE seem to store the downloaded
*ASCII* file with a <LF> (linefeed) record separator, instead of the
(more correct) <CR/LF> record separator. Now, many PC based programs
can read such files with no problem... but ... not WRQ's Reflection
(version 5.10). Reflection (ASCII transfer) takes one look at the
file and says: hey, the "record" is longer than 32,767 bytes.
(It's apparently scanning the data, looking for <CR/LF>.)
Yes, our web server is telling the web browser that the file is
a "text" file. And, we've tried downloading from OpenMarket and
from Apache.
So, the basic problem is: how to arrange things to get the
file downloaded into a form re-uploadable (as an ASCII file) by
a PC-based Reflection. (With the added wrinkle that we don't
want to disenfranchise non-PC users.)
We can't simply turn the file into binary with <CR/LF>'s, because
we know that some portion of the accessors will be on Mac / Unix /
other non-PC machines, where that would screw up.
We can't just change the file type to binary on the 3000, and have
the users upload as binary, because you can't stream a binary file.
(And, we'd prefer not to complicate the upload by saying "upload
into a file via a file equate of ...;rec=40,16,f,binary" and
then "now, use FCOPY and file equates to move the file to an
80 byte ASCII file").
Any suggestions?
thanks,
--
Stan Sieler
[log in to unmask]
http://www.allegro.com/sieler.html
|
