P
Peter Judge
Guest
Just a note that the webhandler/cookie issue has nothing to do with the comment that follows.. The cookie issue is just some poor ABL code. That was one of my first thoughts (way back when). There were a couple of issue with that approach. I wanted to use libcurl, to avoid shelling out and the read/write from disk that would entail. Libcurl had some challenges. The main one relates to POSTs (non-GET) methods. Libcurl calls GETs synchronously but POSTs are async; this means you need a callback to process the data returned by the server. While it is possible to use the libcurl DLL – and I have code that does – the ABL is not re-entrant and this meant I had to write a little C wrapper to (basically) make the POST calls synchronous/blocking. There were also issues with libcurl and writing to files on Windows. This in turn means that someone has to build a DLL which the ABL can call, and this means that either we had to add libcurl into the product or you , dear customer, had to build it. We had a similar situation with the w3c HTTP library that we use for various stuff (we needed a callback). There’s also a question with libcurl around how it integrates with (a) our message/event loop and (b) our SSL infrastructure. Neither of these was a good option at the time. We do use libcurl for some of the OE Auth Gateway stuff so it may be worth revisiting.
Continue reading...
Continue reading...