In trying to publish a large document on the WEB

I found 2 frustrating problems using OI3.4.

1) Trying to use CALL MSG to debug, when the text

string grew longer than 40,000ish the CALL MSG

function did nothing… no error, no message.

2) Passing a ]32000ish length string using

INET_REPOS and submit results in the following

display at the browser "Request timed-out".

Am I exceeding published limits or just finding

them by chance?

abjones,

Are you using INET_MSG? The value you return from an internet procedure must represent a valid HTML script.

gene

I am having trouble with MSG displaying to the

web server monitor when the text string is over

40K (50K for sure). I work with large strings and

always debug using MSG having no trouble in AREV.

I am still learning OI.

If the text string is 33000 length then I get

enough MSG display on the server to see that the

program is working, but that length string will

not be sent to the client; a timeout error message

appears on the client display.

Are there limits less than 64K that I need to be

aware of?

In testing our web publishing through OI (3.5), things are working fine except for when I am returning large documents (above 32k).

I assumed that this was due to some time constraint and endeavoured to implement the Send-Event feature indicated in the 3.4 documentation. This did not change things, although I am not yet convinced that I am implementing this correctly.

However I see that there was an uncompleted exchange in this thread

abjones refers to similar problems with documents above a certain size. He was concerned about hidden constraints on document size when publishing.

Any clarification?

Anthony,

The bug that prevented the processing of HTML pages larger than 32K was fixed in OpenInsight 3.6 (module OICGI.EXE). However, the 64K limitation is still there.

Gene

View this thread on the forum...