4 ms·
It just seems very odd that (2!) people would recommend an "ORM/SOA framework" when all the poster wanted was an HTTP client library. At least you can link to t
by lmz 5y ago
It just seems very odd that (2!) people would recommend an "ORM/SOA framework" when all the poster wanted was an HTTP client library. At least you can link to the HTTP client parts?
- clouddrover 5y agoHere you go: Mormot 1.18 (stable): https://github.com/synopse/mORMot/blob/master/SynCrtSock.pas https://github.com/synopse/mORMot/blob/master/SynCrtSock.pas Mormot 2: https://github.com/synopse/mORMot2/blob/master/src/net/mormot.net.client.pas https://github.com/synopse/mORMot2/blob/master/src/net/mormo... https://synopse.info/files/html/api-1.18/SynCrtSock.html#THTTPCLIENTSOCKET https://synopse.info/files/html/api-1.18/SynCrtSock.html#THT... https://synopse.info/files/html/Synopse%20mORMot%20Framework%20SAD%201.18.html#TITL_135 https://synopse.info/files/html/Synopse%20mORMot%20Framework... They have multiple client implementations. You can pick the one you like (THTTPClientSocket, TWinHTTP, TWinINET, TCurlHTTP, TWinHttpWebSocketClient).
- benibela 5y agoIt is because Lazarus/FPC have no package manager to handle dependencies. It is crippling the ecosystem. If you want to write an oss ORM/SOA framework with HTTP, you cannot use a HTTP client library, because then people cannot compile your framework when they do not have the library installed. You can write in the documentation, they should install the library, but no one reads that. Also, if the library gets an update, it might not be compatible anymore. So you need to bundle the HTTP client in your framework. Now you could write your own or fork one, but in either case you end up with a framework and its own HTTP client.