HP3000-L Archives

February 2001, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Frank Gribbin <[log in to unmask]>
Reply To:
Frank Gribbin <[log in to unmask]>
Date:
Tue, 20 Feb 2001 10:39:19 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (46 lines)
Latest test: With POST sending 600+ characters, 1st LINPUT received 128,
then 138 were lost,  2nd LINPUT received 128, then 78 were lost, 3rd LINPUT
received 80, remainder were lost.  That looks like a data overrun.

The consensus of respondents is to read the STDIN datastream character by
character.  I am trying combinations of BASIC's file reading statements and
MPE FILE equations to find a working match.  Failing that I'll investigate
the READ & READX intrinsics.  Ideas are welcome.

Regards,

Frank Gribbin
Potter Anderson & Corroon LLP


On Mon, 19 Feb 2001 16:38:12 -0500, Frank Gribbin
<[log in to unmask]> wrote:

>Hello all,
>
>I am working with APACHE 1.3.4 on my 928 under 6.5 and have been
>investigating the BASIC V Interpreter as a CGI tool.
>
>#!/bin/sh
>callci basic BTEST
>
>No harassment please ... It loads very quickly and is already IMAGE-
>enabled.
>
>When reading the results of an HTML POST, my program only receives the
>first ~88 bytes / 44 words of data.  For this test, I've tried reading
>STDIN & STDINX with variations of :
>
>  200 DIM R$(240)
>  210 FILES *
>  220 SYSTEM H2,"FILE IN1234=$STDIN;REC=-240,1,F,ASCII"
>  230 ASSIGN "IN1234",1,H2
>  240 LINPUT #1;R$
>
>Any ideas why the limit and how to get around it ?
>
>Regards,
>
>Frank Gribbin
>Potter Anderson & Corroon LLP

ATOM RSS1 RSS2