any general solution for larger size parameters in 3gl interface ?
Author: email@example.com (gerdvassen)
hello everybody !
I am trying to create a callout 3GL interface (via activate), and in different places I am facing limitations of fixed size parameters due to the nature of how this is handled in Uniface. I would like to have my functions work independently of the size of the parameters. The parameters could take 100k or more, even if they most often just take some bytes (please do not ask me to rethink my design, I am looking for a general approach to an ever-returning problem :-)).
I can understand that on a lower level, those fixed packet sizes are necessary, but looking for instance at the UHTTP Uniface component, I can see that Uniface has also found a mechanism to solve this by repeated calls to READ_CONTENT until all the data is read (could probably be handled in a more programmer-friendly way by just doing this internally, but at least there is a way).
Does anybody have had similar or better, more generalized approaches for this issue that could be shared with the community ?