# 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