In that case we'll actually have one Xmir process per app (which is probably OK for resources).
That's more elegant, and more secure, than trying to hack Xmir to emit multiple connections to the Mir server. And it works right now without modifying code.
Also, it appears you can uniquely identify an Xmir instance to the shell already using 'Xmir -mir <appid>'.
In that case we'll actually have one Xmir process per app (which is probably OK for resources).
That's more elegant, and more secure, than trying to hack Xmir to emit multiple connections to the Mir server. And it works right now without modifying code.
Also, it appears you can uniquely identify an Xmir instance to the shell already using 'Xmir -mir <appid>'.