Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 11
    Another solution is to create your own scheme, and have your application handle this scheme's links. So that for example, your application is opened when the foo://bar link is clicked. Commented May 1, 2015 at 20:56
  • Just to clarify - you're suggesting to create an application that the users have to download, then have a file downloaded each time we need to pass patient's info, and have that application open it? Then, that application would basically do what our Java applet does now and pass in the patient's name and ID? This certainly seems possible, albeit clunky. We are going for a lightweight implementation here, and we prefer to not have any client installs since we have users on various platforms, and it goes against the point of our cloud implementation. However, this may be the only solution here. Commented May 1, 2015 at 21:45
  • @RichardTyszka: package it with your desktop application. Clunky sure, but it could be made invisible to the user. Commented May 1, 2015 at 22:45
  • +1 It works. I have done it. In my case from the web me had to pass some data to a remote desktop app. We creates a file with the data, gave it a particular extension, then client-side associated that extension with our remote desktop app, so every time such a file is downloaded, the client machine opens the file with our app. Out app then reads the connection info from the file and stablishes the connection. Commented May 2, 2015 at 1:40
  • 1
    @RichardTyszka: You should first ask each of the image vendor you intend to support to see if they already have defined those "shortcut files" for their own applications. Then, instead of trying to come up with your own, you will simply create and send a shortcut file belonging to the version of vendor software that you know the user is using (and already configured with). Therefore, you do not need to create a Windows application just to dispatch to the third-party software. Commented May 2, 2015 at 8:17