-
Notifications
You must be signed in to change notification settings - Fork 3
/
http_connection.cc
197 lines (165 loc) · 6.8 KB
/
http_connection.cc
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
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
#include <iostream>
#include <string>
#include <tuple>
#include <vector>
#include "protenc.h"
// Example use of the ProtEnc library: an advanced builder pattern.
//
// Here, we have an HTTP connection builder. We want to force the user to add
// one or more headers, then exactly one body, after which he will be able to
// start the connection. ProtEnc will enforce that our object is in the right
// state at every step.
//
// We can represent those constraints as a Finite State Machine (FSM)
// (https://en.wikipedia.org/wiki/Finite-state_machine), which is equivalent to
// a regex. In other words, our protocol looks like the regex:
// (header)+(body)(start)
//
// If we turn that into a FSM, we get:
//
// ******* ********* ******
// *START* ---header---> *HEADERS* ---body---> *BODY* -->build<--
// ******* ********* ******
// | ^
// | |
// header
//
// We start in the state "START", from there we can add a header, which leads
// us to the state "HEADERS". There, we have a choice: we can keep adding
// headers as many times as we want, always looping back to the same state, or
// we can add a body, getting us to the state "BODY". From there, we just have
// to call "build", which is the final transition into an accepting state.
//
// The setup consists of:
// - An enum to list the states.
// - The types describing our state machine (initial states, final
// transitions, transitions, ...).
// - The implementation of the builder, unconstrained.
// - The wrapper class, which will do the constraining.
// Dummy connection class.
using HTTPConnection = std::tuple<std::vector<std::string>, std::string>;
// List of states in our FSM.
enum class HTTPBuilderState {
// Empty class.
START,
// Added at least one header.
HEADERS,
// Added the body.
BODY
};
// Forward-declaration of the wrapper, to make it a friend of
// HTTPConnectionBuilder. That way, we can hide the constructor of
// HTTPConnectionBuilder, preventing users from creating an unwrapped
// HTTPConnectionBuilder.
template <HTTPBuilderState>
class HTTPConnectionBuilderWrapper;
// Basic implementation of the class, without the protocol constraints.
class HTTPConnectionBuilder {
public:
void add_header(std::string header) {
headers_.emplace_back(std::move(header));
}
void add_body(std::string body) {
body_ = std::move(body);
}
// This is a query function: it will just return information, without
// changing the object.
size_t num_headers() const {
return headers_.size();
}
// Start the connection. This should consume the object.
HTTPConnection
build() && {
return HTTPConnection(std::move(headers_), std::move(body_));
}
private:
// Constructor is private, only the wrapper gets to build one, so that
// no one builds a connection starter not wrapped.
HTTPConnectionBuilder() = default;
// Only the wrapper has access to the class, to build it.
template <HTTPBuilderState>
friend class ::HTTPConnectionBuilderWrapper;
// Internal fields.
std::vector<std::string> headers_;
std::string body_;
};
using prot_enc::Transitions;
using prot_enc::Transition;
using prot_enc::FinalTransitions;
using prot_enc::FinalTransition;
using prot_enc::ValidQueries;
using prot_enc::ValidQuery;
using prot_enc::InitialStates;
// Definition of the graph, from the initial states, transitions and final
// transitions.
// The use of aliases allows us to get around the limitations of macros with
// parameters containing commas.
// Initial states (can be a list).
using MyInitialStates = InitialStates<HTTPBuilderState::START>;
// Transitions, of the form <starting state, end state, function pointer>.
using MyTransitions = Transitions<
// We can go from START to HEADERS by calling add_header.
Transition<HTTPBuilderState::START, HTTPBuilderState::HEADERS,
&HTTPConnectionBuilder::add_header>,
// This is the loop: we stay in the state HEADERS.
Transition<HTTPBuilderState::HEADERS, HTTPBuilderState::HEADERS,
&HTTPConnectionBuilder::add_header>,
Transition<HTTPBuilderState::HEADERS, HTTPBuilderState::BODY,
&HTTPConnectionBuilder::add_body>
>;
// Accepting states, of the form <accepting state, end function pointer>.
using MyFinalTransitions = FinalTransitions<
FinalTransition<HTTPBuilderState::BODY, &HTTPConnectionBuilder::build>
>;
// Valid information queries, of the form <accepting state, end function
// pointer>.
using MyValidQueries = ValidQueries<
// We can only call num_headers from the state BODY.
ValidQuery<HTTPBuilderState::BODY, &HTTPConnectionBuilder::num_headers>
>;
// This is the declaration of the wrapper: it is a class declaration.
PROTENC_START_WRAPPER(HTTPConnectionBuilderWrapper, HTTPConnectionBuilder,
HTTPBuilderState, MyInitialStates, MyTransitions,
MyFinalTransitions, MyValidQueries);
// Declare the list of functions that we are wrapping:
// Transitions
PROTENC_DECLARE_TRANSITION(add_header);
PROTENC_DECLARE_TRANSITION(add_body);
// End functions.
PROTENC_DECLARE_FINAL_TRANSITION(build);
// Query functions.
PROTENC_DECLARE_QUERY_METHOD(num_headers);
PROTENC_END_WRAPPER;
// Factory method. Note that trying to build a wrapper in any other state than
// START (because it's in our initial state list) will fail.
static HTTPConnectionBuilderWrapper<HTTPBuilderState::START>
GetConnectionBuilder() {
return {};
}
int main() {
// Get the connection with an easy interface.
// The order of the functions is checked at compile-time by the state
// markers.
HTTPConnection connection_1 = GetConnectionBuilder()
.add_header("First header")
.add_header("Second header")
.add_body("Body")
.build();
// Print the body of the connection, just to check that we succeeded.
std::cout << std::get<1>(connection_1) << '\n';
// The query is only valid once we have the body.
auto connection_part = GetConnectionBuilder()
.add_header("First header")
.add_body("Body");
std::cout << "Num headers: " << connection_part.num_headers() << '\n';
// We have to move the connection_part, because all the operations consume
// the object and return a new one.
auto connection_2 = std::move(connection_part).build();
// This doesn't compile:
// GetConnectionBuilder().add_body("Body");
// GetConnectionBuilder().add_header("First header")
// .add_body("Body")
// .add_header("Second header");
// GetConnectionBuilder().add_header("Header").build();
return 0;
}