1 / 8

The Pieces of MSM-Workstation

The Pieces of MSM-Workstation. John Murray George James Software. Goal. Outline the boundaries between Workstation components described in the “MSM Product Plan” from InterSystems Corporation, so that the consequences of that Product Plan can be better understood. Before proceeding.

rlook
Download Presentation

The Pieces of MSM-Workstation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The Pieces of MSM-Workstation John Murray George James Software

  2. Goal • Outline the boundaries between Workstation components described in the “MSM Product Plan” from InterSystems Corporation, so that the consequences of that Product Plan can be better understood The Pieces of MSM-Workstation

  3. Before proceeding... • I am not speaking for InterSystems Corporation • Formerly Software Engineer with Micronetics Europe (4.5 years) • Design, development and roll-out of MSM-Workstation • 11 years experience in the “M World” The Pieces of MSM-Workstation

  4. Distributed Components • The Engine (the DLL) • Runs M code • Manages access to M databases containing globals and routines, including network connectivity • Provides system service functions for application use • The Tool (the EXE) • GUI development environment • Edits routines, globals, windows and other components • Supports interactive GUI debugging of M code • Creates redistributable EXEs that use the engine The Pieces of MSM-Workstation

  5. The Engine • MSMWS002.DLL • Three elements of the engine • Implementation of X11.1 (M) • Written in C; source shared with MSM-Server • Implementation of X11.6 (MWAPI) • Written in C++ • Service routines • Written in M • Auxiliary file, MSMTCP2.DLL, only invoked if TCP/IP features are used The Pieces of MSM-Workstation

  6. The Tool • MSMWS.EXE • A Workstation-built EXE just like your own • Assembled using a bootstrap process from: • M routines • M globals • Window definitions (VEX files) • Supporting XCall package, MSMDEV.DLL • Built from C sources The Pieces of MSM-Workstation

  7. The ISC Plan • Support and tactical enhancements for the M component of the engine • No support or enhancement for the MWAPI component of the engine, and no changes “other than to fix absolutely critical bugs” • Release the source code for the tool, “so that interested users can enhance it” The Pieces of MSM-Workstation

  8. What does this mean? • Users of the WS tool will be able to fix/improve it themselves, or contract with others who offer such services • ISC support for the M engine should resolve certain types of problem, and yield improvements in areas such as connectivity • Consider the MWAPI portion of the engine as frozen. Develop problem workarounds in your own code, or in the tool’s window code-generator The Pieces of MSM-Workstation

More Related