RESTful triggers

To trigger an event at the moment, it must be done via WebSockets, which requires setting up a WebSocket connection with Warlock session and sending the trigger packet. To ease use in some situations, it might be nice to be able to send triggers via HTTP instead of initating the WebSocket protocol connection. We would use the same listening socket as WebSockets, but instead of looking for the Switching Protocols request, we process it as a normal HTTP request.

This of course will need some level of simple authentication so that not anyone can just send triggers. Whether this is a global key, or what might be better is setting up a list of keys that can possible expire or be revoked. This could be stored in a key file (we can use the BTREE file format) and keys can be added/removed via normal WebSockets protocol commands. These keys can maybe even have ACLS or restrict triggers to a set list, or even be trigger specific so that the key is actually used as the trigger name in the request. This might actually be the best option. Although maybe all of the above which would allow access at different levels.