Changes between Version 4 and Version 5 of GROUP_WRAPPERS_R0
- Timestamp:
- 08/24/09 18:54:02 (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GROUP_WRAPPERS_R0
v4 v5 31 31 <size> <id> ... [[BR]] 32 32 <size> and <id> are mandatory and their meanings are : 33 * size - the length of the integer sequence 33 * size - the length of the integer sequence. The size includes the size number itself. 34 34 * id - command/sequence id 35 35 … … 38 38 The communication will be in the following way: 39 39 * the Java program sends a command through the standard input of the C++ process 40 * the C++ program creates a respon eson the base of the command41 * the C++ program returns the re posne through its standard output42 * the Java program receives the respon e and acts on the base of it40 * the C++ program creates a response on the base of the command 41 * the C++ program returns the response through its standard output 42 * the Java program receives the response and acts on the base of it 43 43 44 This means that the Java program will be blocked until it rec ievesmething from the standard input of the process so the Java wrapper will be in separate thread. Also the control of the C++ application will be in the Java part - it will run and stop it.44 This means that the Java program will be blocked until it receive something from the standard input of the process so the Java wrapper will be in separate thread. Also the control of the C++ application will be in the Java part - it will run and stop it. 45 45 46 The flow of communication written above is common for all other wrap ers and native applications. This code will reside in classes called Bridges. [[BR]]46 The flow of communication written above is common for all other wrappers and native applications. This code will reside in classes called Bridges. [[BR]] 47 47 There will be some common commands and responses: 48 48 * StartCommand