[ ANN ] Release 8.1.0 DP-3

[Charles Warwick]

On 31/07/2016 9:53 am, Alex Tweedly wrote:
>> No, you don’t need to do anything unless you are explicitly selecting 
>> inclusions during the standalone build. Then if you don’t have the 
>> internet library (libURL) included you need to include it as an extra 
>> inclusion. tsNet is resolved as a dependency of libURL. At the moment 
>> we don’t have a facility for turning tsNet off in the event you want 
>> to use libURL (not really sure why you would want that but I guess 
>> it’s possible). You can turn tsNet off if you want to with `dispatch 
>> “revUnloadLibrary" to stack “tsNetLibURL”`
> Q. Why would I want to turn it off ?
> A. for testing.
> If I have a stack that uses libURL, and I want it to be usable with 
> either Indy or Commercial version, then I *should* (IMO) test it with 
> both tsNet and straight libURL. I do not have the Community version on 
> any of my machines, and never will so long as that puts me at risk of 
> unintentionally exposing my stacks to GPL - so I would need a way to 
> turn off tsNet to allow such testing.

I assume you mean "either Indy or Community version" above :-)

To clarify Monte's comment above, if you include libURL in your 
standalone application, the tsNet external will automatically get 
included in the build.  There is currently no way from within the 
"standalone application settings" to disable the use of tsNet with libURL.

However, if you do need to completely disable the use of the tsNet 
libURL driver so that your standard networking calls which utilise 
libURL won't invoke the tsNet commands, you can issue the "dispatch" 
command Monte mentioned above.

This also removes the dependancy links between tsNet and libURL, so that 
the tsNet external will not get included in any standalone build unless 
you manually select it (for example, if you just wanted to use it via 
the tsNet commands).

Alternatively, if you just want disable the use of the tsNet libURL 
driver for testing purposes, but don't want to remove the dependancies 
themselves, you can simply issue:

libUrlSetDriver ""

Note that you can still use the tsNet commands directly (provided you 
include the external if you are building externals) even if you do this.

>
> If I do use some of the tsNet handlers, and then someone else 
> downloads that stack and runs it in the Community version, do these 
> calls simply fail, or are there 'stub' versions included in the 
> community version ?
>
Like any other external that is provided in the commercial versions 
only, the handler calls will fail.

Regards,

Charles