SBarnes wrote:To control the user interface that's a whole different ball game, you would need to build some sort of inter-process communication mechanism such as using a socket
Yep, this would be the way to go.
Create a custom URI Scheme in Windows (just a
few registry entries) and this should launch your own custom .exe which will accept the hyperlink as a parameter, and then using Windows socket or similar send a message.
A plugin in Jiwa will establish a socket to listen on - and receive messages from the custom .exe which you could then act on.
This gets messy on RDS environments where you have multiple Jiwa.exe's running and listening on the same socket / port - you'd have to layer your own protocol within the message to include the Windows username at least and the listener discards all messages not containing that user - or something like that.
Interesting little problem - but I'd budget on a week of time to get it working right - and even then it's a bit clunky in that you need to install a custom executable and custom URI scheme registry entries on each machine running Jiwa.