[ ANN ] Release 8.1.0 DP-3

[Sannyasin Brahmanathaswami]

@Charles:

So, in effect, just to clarify my understanding… 

the *only* difference between the TSnet indy and business license is that the indy user has the added burden of coding explicit tsNet commands to get the same asynchronous behavior that the business user can get with simple calls that were formerly blocking. But otherwise, the exact same asychronous task(s) can be accomplished with either license.

Correct?


On 7/31/16, 10:53 PM, "use-livecode on behalf of Terry Judd" <use-livecode-bounces at lists.runrev.com on behalf of terry.judd at unimelb.edu.au> wrote:

    Absolutely.  You can issue post/get/put asynchronous commands even to
    the same server with the Indy license using tsNet commands directly
    (tsNetGet, tsNetPost, tsNetUpload, etc.. ) or by using non-blocking
    libUrl commands like "load url".
    
    I was referring to the blocking calls, e.g.  "post x to url y", "put x
    into url y".  For these commands, the behaviour of tsNet in Indy is the
    same as the standard behaviour for libUrl.  The script waits for the
    command to return and in the meantime, no other blocking request can be
    made.
    
    In Business however, blocking calls do not prevent other blocking calls
    being made and executed at the same time.
    
    Hope that makes sense?