bleh

TODO

@@ -1,24 +1,36 @@
- - zomp nodes must report the realms they provide to upstream nodes to which they connect.
-   On redirect a list of hosts of the form [{zx:host(), [zx:realm()]}] must be provided to the downstream client.
-   This is the only way that downstream clients can determine which redirect hosts are useful to it.
+- Make the create project command fail if the realm is invalid or the project bame already exists.
 
- - Change zx_daemon request references to counters.
-   Count everything.
-   This will be the only way to sort of track stats other than log analysis.
-   Log analysis sucks.
+- Add a module name conflict checker to ZX
 
- - Double-indexing must happen everywhere for anything to be discoverable without traversing the entire state of zx_daemon whenever a client or conn crashes.
+- Check whether the "repo name doesn't have to be the same as package, package doesn't have to be the same as main interface module" statement is true.
 
- - zx_daemon request() types have been changes to flat, wide tuples as in the main zx module.
-   This change is not yet refected in the using code.
+- Make the "create user" bundle command check whether a user already exists at that realm.
 
- - Write a logging process.
-   Pick a log rotation scheme.
-   Eventually make it so that it can shed log loads in the event they get out of hand.
+- Define the user bundle file contents: .zuf
 
+- Make it possible for a site administrator to declare specific versions for programs executed by clients.
+  Site adminisration via an organizational mirror should not be ricket science.
+
+- zomp nodes must report the realms they provide to upstream nodes to which they connect.
+  On redirect a list of hosts of the form [{zx:host(), [zx:realm()]}] must be provided to the downstream client.
+  This is the only way that downstream clients can determine which redirect hosts are useful to it.
+
+- Write a logging process.
+  Pick a log rotation scheme.
+  Eventually make it so that it can shed log loads in the event they get out of hand.
+
+- Create zx_daemon primes.
+  See below
+
+- Create persistent Windows alias for "zx" using the doskey command and adding it to the localuser's registry.
+  The installation escript will need to be updated to update the windows registry for HKEY_CURRENT_USER\Software\Microsoft\Command Processor
+  AutoRun will need to be set for %USERPROFILE%\zomp_alias.cmd
+  zomp_alias.cmd will need to do something like:
+    `doskey zx="werl.exe -pa %zx_dir%/ebin -run zx start $*"`
+  https://stackoverflow.com/questions/20530996/aliases-in-windows-command-prompt
+  Whatever happens, local users must be able to do `zx $@` and get the expected results.
+  Somewhat more tricky is how to make the creation of shortcuts less taxing on the lay user... ?
 
- - Create zx_daemon primes.
-   See below
 
 New Feature: ZX Universal lock
   Cross-instance communication