Wt

Currently, if you supply the --resources-dir argument to wthttp, then requests to /resources will be sent there.

However, this may not always be the place we want to look for Wt's resources. The location where Wt looks for resources can be
configured differently with the resourcesURL property. Also, if you deploy a WApplication at /deploypath/ (note the
trailing slash), then Wt will look for resources in /deploypath/resources.

We'll have to figure out what we want to do about this. Of course, the user can always not use --resources-dir and copy resources
or use symlinks inside of their docroot, just like before the --resources-dir command line argument existed, but making it possible
to customize where the resources are deployed may be useful. Maybe any resources/... that comes after a /deploypath/ should resolve
to the --resources-dir.