|
|
Make remote tech support as simple as possible
xgeek - the previous article I alluded to at the beginning of the piece describes pretty much exactly what you want to do, I think. It is far more secure - but then I don't know what the chances of (VERY) occasional vnc traffic being intercepted over port 5500 for the duration of a session.
Make remote tech support as simple as possible
to call the application in your bundle (assuming you put it in Content/Resources):
set kVNCserver to quoted form of POSIX path of (((path to me) & "Contents:Resources:OSXvnc-server") as string) do shell script kVNCserver & " -connectHost " & kyour_ip & " -connectPort " & kPort & " -rfbwait 5000 &> /dev/null Where, as previously said, kyour_ip is your IP address, and kPort the port to be used. Doing so, you can put your app everywhere you like and your client has only to double-click it. This is how my wrapper app looks like: http://www.jaw.it/img/rass.jpg As said, I won't post it until I'm sure about vnc licensing.
Make remote tech support as simple as possible
OSXvnc seems to be under the GPL, at least as listed at http://sourceforge.net/projects/osxvnc
I don't know if the GPL nature of OSXvnc requires one to release the code for any GUI wrapper for it. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|