neuray API Programmer's Manual

mi::bridge::IBridge_client Class Reference

[Bridge client]

Description

API component that serves as entry point for the client-side Bridge API. Can be used to create sessions to a Bridge application.

Public Member Functions

virtual const char* get_bridge_protocol_version() const =0
Returns the Bridge protocol version.
virtual IClient_sessionget_session( const char* application_url, const char* security_token = 0) =0
Returns a session to the provided Bridge application running on a Bridge server. More...

Member Functions

virtual const char* mi::​bridge::​IBridge_client::get_bridge_protocol_version() const [pure virtual]

Returns the Bridge protocol version.

virtual IClient_session* mi::​bridge::​IBridge_client::get_session( const char* application_url, const char* security_token = 0) [pure virtual]

Returns a session to the provided Bridge application running on a Bridge server. Bridge supports session sharing, so subsequent calls to this method with the same URL and security token will return an already existing valid session. The session will be considered the same if the URL and security token strings match exactly, otherwise a new session will be created. If a session is closed then calling get_session() with the same URL and security token will create a new session and attempt a new connection to the server.

The session will connect to the specified URL automatically. To find out if the session is connected or if the connection fails add a session state callback by calling mi::bridge::IClient_session::add_session_state_callback(). This callback will be called immediately with the current state, and then when the state changes.

See also:

mi::bridge::IBridge_server::create_application()

Parameters

application_url
The web socket URL to the server-side Bridge application. If the HTTP server listens on host "somehost" and port 80, and the application path on the server side is set to "/myapp", then the client will connect using the URL "ws://somehost:80/myapp". If the connection is encrypted using the SSL protocol, then the prefix "wss" needs to be used instead of "ws". Note that the port must be specified. The standard port for web sockets is 80 and 443 for secure web sockets.
security_token
An optional security token that can be inspected by the server-side application to decide whether the session should be accepted or rejected.