| 103 | | The FEP Simulator communicates with the ATMS via RPC. It sends fep_reply structs which contain traffic condition data. Each |
| | 103 | The FEP Simulator communicates with the ATMS via RPC. It sends fep_reply structs which contain traffic condition data. Each fep_reply struct corresponds to a single FEPLine. |
| | 104 | |
| | 105 | The FEP Simulator includes the generated rpc files: "fep.h", "fep_clnt.c", and "fep_xdr.c". These files need to be included to utilize RPC. |
| | 106 | |
| | 107 | The method used to transfer the fep_replys, from the included rpc files, is named fep_reply_xfer_32(fep_reply *reply, CLIENT *clnt). |
| | 108 | |
| | 109 | fep_reply structs contain metadata and an fep_answer_list struct. An fep_answer_list struct contains a fep_shortanswer_list struct. An fep_shortanswer_list struct contains an fep_shortanswer struct. An fep_shortanswer struct contains an fep_shortanswer_msg struct. The fep_shortanswer_msg contains a char array, which is the actual message that contains traffic condition data. All of these structs are defined in the "fep.h" file. The struct definitions are as follows: |
