aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Boberg <[email protected]>2023-02-08 16:14:17 +0100
committerStefan Boberg <[email protected]>2023-02-08 16:14:17 +0100
commit274f44aff79b8374bdbc0a77c424082189db2614 (patch)
tree28fad3c28405006eabc3b146a0fbda248aaaa49b
parentremoved some deprecated scripts (diff)
downloadzen-274f44aff79b8374bdbc0a77c424082189db2614.tar.xz
zen-274f44aff79b8374bdbc0a77c424082189db2614.zip
removed very old and invalid TODO.md
-rw-r--r--TODO.md49
1 files changed, 0 insertions, 49 deletions
diff --git a/TODO.md b/TODO.md
deleted file mode 100644
index a582bd904..000000000
--- a/TODO.md
+++ /dev/null
@@ -1,49 +0,0 @@
-# General
-
-* Switch to CMake projects for cross-platform builds?
-
-# Connectivity
-
-## Jupiter
-
-* High-performance/concurrency HTTP client (on asio)
-
-## Peer Connectivity
-
-* Beacon / tracker implementation
-* CID store peer fetching
-
-## Downstream Connectivity
-
-
-
-# Runtime
-
-* High performance (HTTP?) client (layered on asio or UE sockets)
- * Do we have asio in the engine yet?
-
-# Local Features
-
-* VFS for surfacing debugging information
-
-# Cache
-
-* Full support for content-type on simple (unstructured) values
-
-# Daemon Notes
-
-When operating in background daemon (Windows Service) mode, there are a few
-additional things to consider:
-
-* Install and uninstall (this will vary by platform)
- * Where is the service installed? How is it uninstalled?
-* Servicing
- * How is the server versioned? I would suggest going with a single release
- number to keep things simple. There should not be any tight coupling with
- different engine branches (new releases should be backwards compatible) etc
- and any service development should take place on a single stream
-
-# Random things
-
-* We currently have too many different paths for marshaling Compact Binary packages. They
- need to be unified to use `FormatPackageMessageBuffer` everywhere