Hi all,
Do you know if the encoding implementation is provided by the new Progress Http Client?
I have a problem when performing a post request against the Rollbase Rest API (so that it supports an UTF-8 encoded input).
When passing data to the RollbaseAdapter with German Umlaut (e.g. Äöüß) my current encoding implementation is not working.
the problem is that the expected returned type is longchar, not character
I see that all the methods work with CHAR Datatype. What if one is using LONGCHAR because the Data to be encoded could be larger than the Progress CHAR limit?
Out of curiosity, do you have practical examples of >32k URL's?
Currently the whole public URI API uses characters (query strings are stored internally as longchars but that's not exposed anywhere).
Changing this would require a call to TS to log a bug, since there's no simple workaround I can see right now.