You're referring to the general Options?

IIRC, the old ASB client auto-detects what's available, and if TCP is blocked, it falls back to HTTP(s).

Yes, I played with these as well but mean the (same) settings in the File -> Connect window.

What's the difference to the new client?

When getting the entities that populate the tree, https is always used. I doubt that you can change that since it is handled inside the client.

The Connectivity Mode determines what is used for sending and receiving messages.

What's the difference to the new client?

The new client is only used in a few places in the code. One of them is when purging messages. The new client supposedly only uses AMQP. However, I believe it is using https just like the old client for getting entities. It is Open Source though...

Thanks to the 3 generations of the SDKs, there's a lot of confusion. My attempt to clarify that.

Management operations

• Always via HTTP
• Latest SDK has an exception for Filters that can leverage the transport used for the messaging operations

Messating operational

• Latest SDK: single transport AMQP (default) or WebSockets (HTTPs), no auto-detection
• Previous SDKs - AMQP and HTTPs with auto-detection. This is what SBE is using

Protocol

• Always AMQP
• Version 1.0 (no support for 0.9)

Hope this helps.