istio-injection=disabled/enabled ） http http http http http http http Result: can access reviews-v1, reviews-v2 and reviews-v3 Access productpage #IstioCon Istio Identity Istiod Istio Agent Envoy 1. Start to send request: can access reviews-v1, reviews-v2 and reviews-v3 can reach v2 as peer-authentication only defines behavior of server side and auto-mTLS is on by default Access productpage 1) Apply and ingress host to send request: can access reviews-v1, reviews-v3 can not access reviews-v2 since we have enabled ISTIO_MUTUAL mode on client side Access productpage 1) Apply destination rule

NativeScript come to be? Swift/Obj-C Java .NET We ❤ Web. But… We need: • Better offline support • Access to all device APIs • Home screen availability • Push notifications • App monetization • App store JS/TypeScript • Angular Support (or not ?) • 100% Day 0 API Access • Everything Runs on UI Thread* • Plugins created with native code • React Support • API Access via Native Modules • UI Thread vs JS Thread • Angular/Vue/Vanilla existing skills/teams • Reuse existing libraries • Native UI (no WebView!) • Full access to device APIs • Immediate access to new OS features ? Fast to market ? Best experience Intro to NativeScript

layouts • Functions and objects defined in loops • Statements like debugger, eval, with. • How to access Native Engine information • Object class modifications. Threading • In NativeScript by default default everything runs on the main thread. This design has both pro’s and cons • Pros: Easy access to anything dealing with GUI • Bad: Jank when doing lengthy work • Potential Solutions: Worker thread --allow-native-syntax to v8Flags V8 Natives • Docs: https://github.com/NathanaelA/v8-Natives • Gives you access to low level engine information. Things like: getHeapUsage(), deoptimizeNow, optimizeFunctionOnNextCall

// cat ox }18 atomic_ref19 atomic vs. atomic_ref • atomic: atomic access and storage for T • atomic_ref: atomic access for separate T • Scenarios (see P0019R8): • Distinct single-threaded and print(classic); print(array{4, 5, 6}); print(vector{7, 8, 9}); }24 Contiguous > Random-Access • Can we print(deque{-1, -1, -1}); ? • candidate function not viable: no known conversion from

VIP using a load balancer • Two types • ClusterIP provides in-cluster access • NodePort provides out-of-cluster access • Major modes • Iptables • IPVS Iptables mode • How it works • DNAT at

OCI Compa tible Dedicated Docker Image Impleme ntation Language Open source Hot plug Direct access to HW Required Hyperviso rs Backed by Runc Yes Yes Golang Yes No Yes None Docker gVisor+runsc Agent gVisor Guest Kernel O C I Gofer container container Pod Sandbox Sentry KVM/ptrace File Access OCI Implementation Limited Syscall H O S T K E R N E L Comparison Solution Typical

multi-reader pointer. set HP to A if SRC == A clear HP 2 3 6 if HP != A HP Safe to delete A A 7 8 SAFE ACCESS If a hazard pointer points to an object before its removal, then the object Reclamation Beyond Concurrency TS2 – Maged Michael Protector Remover / Reclaimer Hazard pointers protect access to objects that may be removed concurrently. SAFE RECLAMATION Concurrency TS2 Essential Hazard Pointer

value() 会检测是否为空，空则抛出异常 • 当 ret 没有值时（即 nullopt ）， ret.value() 会抛出一个异 常，类型为 std::bad_optional_access 。 optional ： operator*() 不检测是否为空，不会抛出异常 • 除了 ret.value() 之外还可以用 *ret 获 取 optional 容器中的值，不过他不会 std::get • 要获取某个类型的值，比如要获取 int 用 std::get 。如果当前 variant 里不是 这个类型，就会抛出异常： std::bad_variant_access 。 • 此外，还可以通过 std::get<0> 获取 variant 列表中第 0 个类型，这个例子中 和 std::get 是等价的。 variant ：判断当前是哪个类型用

， [] vector ， array ， deq ue random_access_iterator 迭代器外包装 和他所包装的迭代器保持一致 reverse_iterator 和所包装的迭代器一致 https://en.cppreference.com/w/cpp/iterator/random_access_iterator https://www.cplusplus.com/re

where, how, and when work should happen … including some standard ones: an event loop, portable access to the system execution context, nursery for spawned work4 P2300: STD::EXECUTION Proposes: • libunifex) • a timed_scheduler concept and time-based async algorithms; e.g., timeout(). • portable access to a “system” scheduler, backed by e.g., Windows Thread Pool or GCD • a manual event loop scheduler