D
dbeavon
Guest
OK, Thanks for the feedback. I figured something like that was going on, which is why I was hoping to take a peek at the source. The API is fluent (which I really like, so long as it is fast). But of course one big problem with ABL is that every single method call has a measurable performance penalty. Any chance of open-sourcing this stuff? I'd love to be able to see what the fluent "builders" do, so that I can pick-and-choose only the portions that I need.... It takes every trick in the book to squeeze performance out of ABL. The Microsoft.Net-based approach described in the following KB ended up getting me down to about 3 ms round-trips on my REST client calls. (I will be using this as an optimization for WIN32 deployments). knowledgebase.progress.com/.../Is-there-an-HTTP-client-for-OpenEdge I see a growing number of pl/OO libraries in recent versions of OpenEdge. How does Progress choose when to compile an API like this down to machine code (instead of leaving it as r-code)? I think there are some relatively new things they've added (eg DOM/SAX for XML) that are fast because they are built into the AVM itself. I don't see why HTTP stuff can't be done the same way...
Continue reading...
Continue reading...