SetMap::Response> response); void generate_path_service( const std::shared_ptr request, std::shared_ptrResponse> response); bool SetMap::Response> response); void generate_path_service( const std::shared_ptr request, std::shared_ptrResponse> response); bool SetMap::Response> response); void generate_path_service( const std::shared_ptr request, std::shared_ptrResponse> response); bool

text) { auto body = http::UrlEncode({"text", text}); auto response = http::Post("https://www.online-spellcheck.com", body); return response.body; }motivating example std::string SpellCheck(std::string text) { auto body = http::UrlEncode({"text", text}); auto response = http::Post("https://www.online-spellcheck.com", body); return response.body; }motivating example std::string SpellCheck(std::string text) { auto body = http::UrlEncode({"text", text}); auto response = http::Post("https://www.online-spellcheck.com", body); return response.body; } you have to wait! whether you end up writing code

= figureLimit(); return y;} Singleton or Not ?// Original Code with singleton in processor.cpp Response sendData(const Data& data) { Request req; // Transform Data into Request // ..... return CommS Singleton sendData(...) Req Data send Resp// Original Code with singleton in processor.cpp Response sendData(const Data& data) { Request req; // Transform Data into Request // ..... return CommS agencies • Allow dependency injection for testing purposes Bloomberg 12Bloomberg 13 // processor.cpp Response sendData(const Data& data, CommSingleton* comms) { Request req; // Transform Data into Request

applications and shared C++ libraries© 2018 Bloomberg Finance L.P. All rights reserved. 4 Prologue In response to a recent Request for Comment (RFC), a colleague complained that we had violated “the principle encoding choice): class Client { public: template RESPONSE, typename t_REQUEST> int sendRequest(t_RESPONSE *response, const t_REQUEST& request, class Client { public: template RESPONSE, typename t_REQUEST, typename t_CODEC> int sendRequest(t_RESPONSE *response, const t_REQUEST& request

guaranteed response time ❖ Flexible Timing (5-10 milliseconds) ❖ ! A guaranteed response time Hard/Soft Real Time Requirements❖ Flexible Timing (5-10 milliseconds) ❖ ! A guaranteed response time constraints are extremely strict ❖ A guaranteed response time ❖ Microseconds❖ Timing constraints are extremely strict ❖ A guaranteed response time ❖ Microseconds ❖ Flight control system ❖ Flexible Flexible Timing (5-10 milliseconds) ❖ ! A guaranteed response time ❖ Milliseconds ❖ Home automation Hard/Soft Real Time RequirementsWhat level of time precision does our system require?What level

off the current thread? Delaying response to external events can have undesirable consequences:Why do we need to move work off the current thread? Delaying response to external events can have undesirable window if it doesn’t respond to eventsWhy do we need to move work off the current thread? Delaying response to external events can have undesirable consequences: Microsoft Windows will grey-out the entire doesn’t respond within a reasonable timeWhy do we need to move work off the current thread? Delaying response to external events can have undesirable consequences: Microsoft Windows will grey-out the entire

○ Generated headers? ○ Generated sources? ○ Generated input files (-include, -fmodule-mapper=, response files) ● C++ modules… Compilation Databases: Limitations 2 9C++ Modules on the Scene ● Modules Information about module usage ■ Currently CMake “smuggles” through module mapper files (basically response files) ■ These files are referenced by but not necessarily present with the compilation database ○ clang-scan-build ○ clang-tidy ○ IDEs ● Structured response files for argument representation ○ https://wg21.link/P3051 “Structured Response Files” by René Rivera ● Header unit support ● Adding

Coms coms_; void execute(const Action&) { Request req; //... auto result = coms_.send(req); check_response(result); } }; // Com.cpp Result Com::send(const Request& req) { ... return result; } /* Test/Com BasicsBloomberg 42 Dependency Injection Basics Com execute(...) Req Action send result// Dispatches Response Execute(..., Com&); Bloomberg 43 Method Dependency Injection Com execute(..., &) Req Action Dependency Injection Basicsclass Processor { public: // Constructors Processor(...); ... // Dispatches Response Execute(..., Com& com); ... }; Bloomberg 47 Dependency Injection Basics Com execute(...,

Security vulnerabilities in open-source code Solution 6: Vulnerability monitoring, prevention, and response •Review public CVE databases (e.g. GitHub Advisory Database) •Run static analysis + dynamic analysis Security vulnerabilities in open-source code Solution 6: Vulnerability monitoring, prevention, and response •Make it trivial to update packages so you can respond quickly • Track 3rd party code as explicit for sources needed to build dependencies 6. Develop a vulnerability monitoring, prevention, and response strategy and associated tools / workflows 7. Centralize common dependency management tasks, enforce

request Server (back-end) accepts or rejects Response streamed until final message or until client requests cancel Server acknowledges cancel After response connection is ready for another request Server struct /* ... */ { std::chrono::duration<...> delay(); void complete_write(); }; 18 19 After Response Latency can cause client and server state to briefly desynchronize Consider following sequence of