Skip to main content

Client ↔ user to access Server

References​

  1. Software Server ↔ Software to control how Client access content hosted on Server

  2. Dynamic Web Server ↔ Static Web Server with extra Software to update/generate Dynamic Content to send Client

  3. Static Web Server ↔ Computer Hardware run HTTP Server Software to send Static Content hosted files to Clients

  4. User agent spoofing ↔ to send fake User Agent string to announce as different Client, avoid Browser Fingerprint

  5. Thick Client ↔ Browser Client to hold more logic & client-side interactivity

  6. Thin Client ↔ Browser Client only req to display (pre-rendered) static content from Server

  7. Create ↔ (ability for Client) to create data ⇒ POST HTTP Request

  8. Read ↔ (ability for Client_) _to read data ⇒ GET HTTP Request

  9. Update ↔ (ability for Client) to edit/update data ⇒ PUT || PATCH HTTP Request

  10. Destroy ↔ (ability for Client) to delete/destroy data ⇒ DELETE HTTP Request

  11. WebSockets ↔ Web API to open 2-way Client/Server connection, to push update vs Polling

  12. Web Storage API ↔ Web API to persist data stored in Client across session || windows

  13. Client Component ↔ FC to render on Client dynamically

  14. Static Content ↔ fixed content to deliver to Client w/o need to generate/process/modify

  15. Edge ↔ Buzzword for Server to deploy closer to Client.

  16. JS Bundle ↔ single combined JS Code output for Client to run, often Transpile to ES6 for compat

  17. Client State ↔ state store by Client (Browser), TSC

  18. Client-owned ↔ Client State store local & private to Client

  19. Remote ↔ of Server State to store on remote Backend, w/o Client direct access/control over state

  20. Persistent ↔ of Server State tend to be stored for longer between Client sessions

  21. HTTP Cookie ↔ data sent from Backend to Client to TPS

  22. XSS ↔ Exploit to inject naughty code into Client thru Website

  23. polyfill-library ↔ Lib to request Online API to remotely load Polyfill Bundle based on UA Client. cur ver v3

  24. Peer ↔ Bittorrent Client instance connect to Swarm || user to connect to P2P

  25. libtorrent ↔ FOSS Bittorrent Client, C++, lib for many clients

  26. online ↔ boolean for Client online status

  27. Shadowsocks ↔ Client to route traffic through SOCKS5 Proxy. FOSS. not dead?

  28. [WinOS](windows) [Shadowsocks](shadowsocks) [**_Client_**](client) ↔ github.com/shadowsocks/shadowsocks windows/releases/tag/4.4.1.0

  29. Orbot ↔ Android Tor Network Client abandonware?

  30. Anonymous Proxy ↔ Proxy to hide Client IP & only reveal Proxy IP

  31. Transparent Proxy ↔ Proxy to reveal Client IP + Proxy IP

  32. to reduce bundle size ↔ keep Deps on Server Component, min Bundle for Client

  33. Geo-Distributed Cache ↔ to Cache in more spread-out Proxy instances, to reduce Latency to Client

  34. Forward Proxy ↔ Proxy sit in front of Client as gateway to forward Reqs to Internet

  35. socket.io ↔ Node.js Module to build WebSockets with built-in Server/Client & fallback Long Polling

  36. DDoS Protection for Typesense ↔ Proxy Typesense node through DDoS service ie Cloudflare DNS gateway to expose Client

  37. TTFB ↔ Time To First Byte - Server/CDN Latency to send first byte to Client