2016-07-20 3:45 Michael Van Canneyt :
Because all Pascal TCP toolkits out there offer a HTTP Client. (lnet, indy,
> synapse). By doing this, I leave the choice up to the user which one to use
> for various APIs that are built ON TOP of HTTP.
>
> Your use case is simply one I didn't foresee,
> Beca
On Tue, 19 Jul 2016, African Wild Dog wrote:
2016-07-19 4:52 GMT-03:00 Michael Van Canneyt :
1. The whole point of TFPHTTPClient is exactly to couple it to sockets
framework (fcl-net).
If you want to use synapse, use httpsend. lnet has a similar component
for the http protocol.
2016-07-19 4:52 GMT-03:00 Michael Van Canneyt :
>
> 1. The whole point of TFPHTTPClient is exactly to couple it to sockets
>framework (fcl-net).
>If you want to use synapse, use httpsend. lnet has a similar component
>for the http protocol.
>
>
I dont want to use synapse. I am developi
Hello,
This will not be applied, for 2 reasons:
1. The whole point of TFPHTTPClient is exactly to couple it to sockets
framework (fcl-net).
If you want to use synapse, use httpsend. lnet has a similar component
for the http protocol.
2. I favour the opposite approach. Abstract out the
Hello,
The current version of the TFPHTTPClient (the one shipped with fpc 3.0) is
coupled to the fpc's sockets framework (fcl-net) so we can't utilize other
tcp connection framework (e.g Synapse) to perform HTTP requests using
TFPHTTPClient.
I have made an improvement to the TFPHTTPClient class (
