Of course wwIPstuff.dll is mandatory to have good response time.
At least we could have something working also in case we don't have it available.
We could add an ASSERT in case wwIPstuff.dll is not available and string exceeds a given length.
We can't do that because this is used extensively for POST data. If you have a large POST buffer VFP's performance is absolutely terrible. The wwIPStuff code is there because it faster by orders of magnitude minus the small overhead of the API call. In testing I did a long while back the breakeven point is around 250 characters - after that wwIpStuff is faster - for buffers over a a couple of k it's twice as fast, for buffers of 10k it's an order of magnitude faster.
So - the short answer is we can't get rid of it.
+++ Rick ---
Hi,
Suggestion to make URLdecode() and URLencode() work without wwIPStuff.dll
FUNCTION URLDecodeLPARAMETERS lcText,llUtf8DecodeLOCAL lnSize, lnLoc, lcHex, lnHex, lcRetval, loEval, loRegEx
loRegEx = GetRegExObject()
IFLEN(lcText) > 255;
AND File('wwIPStuff.dll')
...