libURL and New TsNet Commands/Failures

[Charles Warwick]

On 1/08/2016 2:40 pm, J. Landman Gay wrote:
> On 7/31/2016 10:46 PM, Sannyasin Brahmanathaswami wrote:
>> AHA.. Yes, "Previous request not complete"
>>
>> how do we get to these results?  "show up in the log " what log?
>
> Sorry, I should have said "my log". My app keeps a text file log of 
> every server transaction that fails. LibURL errors will be in "the 
> result" if something goes wrong.
>
The "Previous request not complete" message comes from the libUrl 
library and will still be generated when using tsNet with the Indy version.

>
> In my case I don't want to terminate the process, since it's important 
> that every transaction completes. Unless there's a fatal error, the 
> app must wait until the data is sent. The problem I have been working 
> around is that the user sometimes continues to execute actions that 
> require a subsequent transaction and if the first one hasn't completed 
> yet, the error occurs (usually because their connection is slow or 
> they're moving very quickly through the app.) I've got something in 
> place that works most of the time, but not having the problem at all 
> would be a big plus. I think asyncronous transactions and the much 
> faster tsNet external may solve that.
>
Sounds like a perfect job for asynchronous connections or the Business 
edition :-)

Regards,

Charles