At 14:28 17.09.1997 -0700, you wrote:
>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.
...
>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>.)
...

Stan,

I'm horribly late with my reply, but nevertheless...

You might cope with the CRLF vs LF problem on the PC side if the
PC users edit the file with the freeware PC editor called PFE (for
Programmer's File Editor). It can handle both line delimiter styles,
DOS (CRLF) as well as Unix/Posix (LF only). The "Save As" dialog
box has an option field in this regard.

See http://www.lancs.ac.uk/people/cpaap/pfe/ for details.

Regards, Lars.

PS: I assume that the PC users have a need to use a terminal emulator
    to upload to the 2nd 3000. If they could use Samba they might simply
    save the file to the network drive (or drag and drop) and it would
    end up being bytestream on the 3000 (which should STREAM fairly well).

    You might even try setting up a "dummy printer" in the Samba config
    that will receive the PC file and STREAM it instead of pushing it to
    the MPE spooler. Contact me if details are of interest.

PS PS: Pardon me for "plugging" Samba again. It is *not* meant as *the*
       universal solution to *all* client/server problems, but sometimes
       there are unexpected niches where it might fit in.