Applies to
TRPCBroker component
Declaration
property DisconnectMode: enumerated;
Description
Enhancements to how the Broker manages multiple connections make this property unnecessary. Consequently, it is being phased out. For now it has been "demoted" from published to public declaration. This means that this property will no longer be visible in the Object Inspector, however, the application will still compile. At run-time it is ignored.
If your application uses more than one Broker component, you should be aware of the component's connect and disconnect behavior.
This property was used to set the mode that determines when your application disconnected from the server. It could be set to one of the following values:
ManualDisconnect: With this setting, the TRPCBroker did not try to disconnect from the server when it was destroyed. This setting was used when there were multiple Broker components in your application and it was not the last Broker component to be disconnected.
OnDestroy: This setting was used to disconnect your application from the server when the TRPCBroker component was destroyed. This was used if you only had a single Broker component or it would be the last component to be disconnected when you had multiple Broker components.
The DisconnectMode property that was made available with the RPC Broker Development Kit (BDK), released in October 1995, is now obsolete and slated for removal from the RPC Broker component (i.e., TRPCBroker).