#20 Devuser enhancements

[Scott Turner]

Several proposed enhancements for development mode
aimed at enhancing ability to support multiple
developers and projects with one broker.

- Ability to specify db connection sets by devuser.
This would facilitate developer specific test
databases and avoid table name conflicts where db
references are in the table.column form rather than
the db.table.column form. Of course their is nothing
to prevent a single developer from having multiple
devuser names, presumably for different projects.
Current connection set logic adds connections but
never disconnects a set. This new feature would have
to disconnect all current databases before connecting
new ones.

- Ability to clear the current devuser setting.

- Ability to name runlog files by devuser so that
debug messages are not intermingled.

- Maintenance of devuser settings in a separate file.
Perhaps <brokername>.<devuser>.ini. This would allow
changes to take effect immediately without resetting
or restarting the broker and all agents.

- An option for restricting the directories or files
where the workshop tools operate by devuser.

- Abilty to password protect a devuser login.