Browse Prior Art Database

Improved Communication between Windows Applications

IP.com Disclosure Number: IPCOM000118678D
Original Publication Date: 1997-May-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 2 page(s) / 61K

Publishing Venue

IBM

Related People

Kinchen, JE: AUTHOR

Abstract

Communications between Windows applications (which includes starting the application, if necessary) typically proceeds as follows: 1. Application A (APP_A) checks to see if Application B (APP_B) is running. APP_A could search the Registry for a predetermined value set by APP_B or enumerate the running Windows applications looking for a match on either the application class or main window caption. 2. a. If APP_B is not running: APP_A can start APP_B using WinExec()/CreateProcess() for example. b. If APP_B is running: APP_A can send a message to it.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Improved Communication between Windows Applications

      Communications between Windows applications (which includes
starting the application, if necessary) typically proceeds as
follows:
  1.  Application A (APP_A) checks to see if Application B
       (APP_B) is running.  APP_A could search the Registry for a
       predetermined value set by APP_B or enumerate the running
       Windows applications looking for a match on either the
       application class or main window caption.
  2.
      a.  If APP_B is not running:  APP_A can start APP_B using
           WinExec()/CreateProcess() for example.
      b.  If APP_B is running:  APP_A can send a message to it.
           In order to do this, it usually requires the following
           information:
          Window handle - This can be retrieved from the
           information returned on the enumeration match
           outlined above or by prior arrangement with
           APP_A (e.g., entry in the Registry).  It can be
           bypassed by using BroadcastSystemMessage() API
           call.  However, this call is not available on all
           WIN32* platforms.  Also, it would depend on APP_B
           having previously registered a unique message
           identifier.
          Message ID - Unless it was a standard Windows message,
           this can be retrieved using RegisterWindowMessage ()
           API call.  This is dependent on knowing the unique
           message string used by APP_B to register the message
           identifier.

      The process outlined above relies on APP_A either having a
prior arrangement with APP_B or APP_A needs logic to determine
certain information pertaining to APP_B....