* Remote invocation of methods

  This seems like it could be implemented with two additional parameters, /computer and /domain. /computer would cause the selected action (if supported) to be carried out on the remote computer. Likewise, /domain would carry it out on an entire group of computers in a domain.
  
* Installation procedures that can be broken up over multiple reboots

  The idea for this is fairly simple. Move the "reboot" attribute from the package defination onto the command defination. To support it, we need to add a new attribute to the command defination in wpkg.xml, "complete". When a package is installed, the defination is immediatly copied to wpkg.xml, with complete false. As each command is run, it is marked complete. When a command requires a reboot, the system is rebooted. Upon startup, wpkg.xml is first parsed for packages that are installed, but with incomplete commands. These commands are resumed. The package is completed and the script moves on. This requires little restructuring. Mostly, since the code just deals with nodes, we can substatute a node from packages.xml for a node from wpkg.xml, and it should continue to run fine.
  
  Upgrading is handled the same. The package node in wpkg.xml is immediatly replaced with the new uncompleted version, and then the commands from the upgrade section are run. This relies on not needing the old version of the node as soon as a package upgrade has been initiated.
  
  Removal is not any different. The remove commands are marked incomplete and the same logic takes hold.
  
* Subsystems

  It seems like a good idea for wpkg itself to only deal with the basics, running external commands. However, a proper package system has much more. Some examples include creating Windows shortcuts in the start menu, running commands per-user as they log on and off, creating quick launch icons. These can be implemented in seperate scripts, that way they are useful on their own. They can be hosted along with wpkg however.
  
* Service Startup

  We need our own Windows service! It could accept remote RPC commands and all sorts of things. However, that's extremely difficult.
  
* Windows Hotfix Scanner

  Write a utility to take the output of Microsoft's patch database (mssecure.xml) generate package entries for them. Awesome idea.
  
