Andy,
1.
would it make sense to also have following command:
CID_QUERY_OWNED_PROCESS_LIST
Data:
no data
response: CID_OWNED_PROCESS_LIST
response data:
Bytes
0-3: number of processes "owned" by the process controller (=processes started
by it)
Remaining bytes: Process IDs as 64 bit unsigned
integers
Each
client easily can keep track of the processes it has launched through the
process IDs returned to it after launch, but in some cases it might be useful to
know all the processes that have been launched by the process controller if
it is an agent accessible by multiple clients
simultaneously.
In
expanding on that thought, following commands might also be useful
then:
CID_QUERY_EXEDESCRIPTOR_LIST
Data:
no data
response:
CID_EXEDESCRIPTOR_LIST
response data:
Bytes
0-3: number of descriptors currently known to
the process controller
Remaing bytes: EXE descriptor IDs as 4 bit unsigned
CID_QUERY_EXEDESCRIPTOR
Data:
EXE descriptor ID as 4 bit unsigned
response:
CID_EXEDESCRIPTOR
response data
Bytes
0-3: XML fragment length
Remaining bytes: EXE descriptor as XML fragment
2.
CID_LAUNCH_PROCESS
what
will be returned when the descriptor ID is the ID of a descriptor group (as
mentioned in the specification of
CID_CREATE_DESCRIPTOR_GROUP)?
maybe
an alternate response:
CID_GROUP_LAUNCHED
response data:
Bytes
0-3: Number of processes launched
Remaining bytes: ProcessIDs as 64 bit unsigned
Luc
Here is the process controller
interface document I referred to last week. This refers to the new HCE
protocol.
-Andy
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
|