-
Notifications
You must be signed in to change notification settings - Fork 0
/
response_messages.fbs
42 lines (33 loc) · 1.26 KB
/
response_messages.fbs
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
// Author: Aniruddha Gokhale, Vanderbilt University
// Created: Sept 2021 for Distributed Systems course
// Modified: Fall 2022 for Computer Networking course
//
// IDL schema for the data type we will be transferring
// For our assignment, we will be defining some application-level
// message formats, just like HTTP has GET, PUT, POST etc.
//
// We have to define a namespace under which this schema gets
// translated to the programming language we are using.
// Let us call it CustomAppProto
namespace proto.response_proto;
// define the user-defined type that we want to serialize
// This can be arbitrarily complex. Here we show a sample
// which is not overly complex but still showcases the features
//
// In your case this structure will be whatever is the data structure
// that holds the information that the producer will send to consumer
// The data structure is defined using the keyword table as shown. The
// variable name is my choice. Individual fields of the data structure
// use the form <variable name: data type>. Note, this can be nested, and
// there could be multiple such data structures defined.
enum Code_Type: int {
OK = 0,
BAD_REQUEST = 1
}
table Response_Message
{
type: int;
code: Code_Type;
contents: string;
}
root_type Response_Message;