P
Peter Judge
Guest
If you want to optimise for Win32/64 you should look into creating your own implementation of an IHttpClientLibrary; that way you can keep the public/client-dev interfaces as-is and just swap out the implementations. There are a couple of places where the HTTP client is slow/inefficient - one big one is in how we deal with the HTTP message bodies: since the ABL does not (yet) have a natively dynamically-expandable MEMPTR structure, this gets done in ABL which is quite a bit slower than it'd be in the AVM. That said, in 12.0 (for which there's a new ESAP "coming soon") we changed the implementation of the ABL ByteBucket to use a native structure (a Progress.IO.MemporyOutputStream). That will be faster, although I've not tested yet exactly how much faster.
Continue reading...
Continue reading...