It does, but is version dependent. It looks like you need at least 12.2 for the server side. See Progress Documentation
For the ABL client side, support for client certificates was added a few releases later. Like 12.4 and 12.5 if memory serves.
Given that you're load-balancing, I'd think yes. You're already using networked db connections so there's no consideration of performance impact there.
I'd be curious why the load-balancing is in pairs when there are 4 AppServer brokers. But regardless, if you load-balance across a pair of...
In some later OE versions (12.3 I think, and the roughly-equivalent 11.7.8 update), the INDEX() function has been enhanced to support using a MEMPTR as a source. This means you don't need to copy the MEMPTR to a LONGCHAR and back.
define variable iPos as int64 no-undo.
iPos = index(v_ptrXML...
I agree on using the WEB transport over REST.
It's all in ABL, so debugging becomes simpler (for us ABL developers)
You can return any MIME type - not just the binary that @Jean-Christophe Cardot mentions, but also things like multipart messages or custom/vendor content types
You get far more...
The AVM does not let errors "past the WAIT-FOR". If there are unhandled errors, the AVM will itself display any errors (or let .NET deal with them).
In .NET terms, you need to add catch blocks to all event handlers, and deal with the errors there. That could be showing errors in some form of...
You can migrate "classic" webspeed to PASOE using the (shipped) CompatibilityHander. In the development server it's the default handler - so in a dev environment you can test easily.
If you want to write new code then you need to add your own WebHandlers. You can use them to process/handler a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.