Just to make sure: this isn't supposed to be a rant about a (admittedly stupid) bug but more of a question if I did not miss something because I know that you can plug the request and response components together and that some properties are set up depending what class the owner of one of them is.
Sorry if I over stepped the mark - just having a little bit of fun. Yes, it doesn't help you but just maybe, a little smile was brought to someone's face. Again, sorry.
It's obvious they don't unit test their code...
ReplyDeleteCould it be for a future version of Delphi, that is running on a quantum computer? ;-)
ReplyDeleteJust to make sure: this isn't supposed to be a rant about a (admittedly stupid) bug but more of a question if I did not miss something because I know that you can plug the request and response components together and that some properties are set up depending what class the owner of one of them is.
ReplyDeleteSorry if I over stepped the mark - just having a little bit of fun. Yes, it doesn't help you but just maybe, a little smile was brought to someone's face. Again, sorry.
ReplyDeletehttp://docwiki.embarcadero.com/Libraries/XE7/en/REST.Client.TCustomRESTClient.PostEntity
ReplyDeleteEmbarcadero Technologies does not currently have any additional information.
This means it's an "undocumented" or imcomplete or buggy API. ;-) haha.
No REST for the wicked? Is the destruction conditional in some way?
ReplyDeleteLars Fosdal Nah, its creating a TRestRequest in that method and then returning LRequest.Response.JSONValue which gets destroyed along with LRequest.
ReplyDelete