Limitations for the IMC Proxy

Owned by Christian Borch
Last updated: Jun 15, 2022
1 min read

With the RESTification of the ModuleAPI and IMC components, HIMSA has been technically forced to introduce some changes to IMC.

The change is that direct communication via references “pointers“ (.Net remoting proxies) between IMCClient and IMCServer is not possible via a REST interface.

HIMSA will appreciate any feedback if the list of possible data types supported in the REST Api does not cover your previously released Noah 4 or Noah 3 modules. Your feedback will enable us to comply with data types previously used in IMC communication and, hence, make the REST interface fully backward compatible. These types apply for both Command and DataReady and the two objects in IMC2 ClientWindowsHandle and ServerWindowsHandle which are found in ShowModuleEx.

Data types can be as follows:

Himsa.IMC2.DataTypeDefinitions for IMC Protocol 2

  • MeasurementConditions

  • ShowModuleEX

  • SignalProperty

  • TargetConditions

  • TargetCurve

  • MeasurementTypes

  • ProbeCalibration

  • PrepareSystem

  • ShowModule

  • SoundLevel

  • DataReady

  • TargetData

  • ErrorInfo

  • TargetPoint

  • MeasurementPoint

  • ClearCurves

  • CouplerCodes

  • SignalProperties

Other types - for protocol 0 and 1 and for IMC2 ClientWindowsHandle and ServerWindowsHandle.

  • System.String

  • String[]

  • Int32[]

  • Int32

  • System.IntPtr - Used for ShowModuleEX - Window handle

  • System.Collections.Generic.List1[System.Int32]

  • System.Collections.Generic.List1[System.String]

Â