userapi: signals

[Peter da Silva <peter-dragonfly@xxxxxxxxxxx>]

Any thought of how signals will be handled once there's nothing but 
messages? For most cases, they could be done in the user API when you 
Wait() on the system message port, but that won't stop a program that's 
in an infinite (or just very long) loop.

The easy solution would be to have a background thread that was always 
live that just handled signals, either by sleeping on a port or by being 
the interrupt handling thread for that process, no?