realbasic-nug
[Top] [All Lists]

Re: Securing Client Server Communications?

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Re: Securing Client Server Communications?
From: "lists@mgreg" <lists@mgreg.com>
Date: Fri, 29 Aug 2008 20:27:54 -0400
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <C4DDDF0A.7BD5E%heizer1@llnl.gov>
References: <C4DDDF0A.7BD5E%heizer1@llnl.gov>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com

On Aug 29, 2008, at 8:14 PM, Charles E. Heizer wrote:

I thought about SSH tunnels but decided against it since I would like to use a web interface at some point.

Thanks,
- Charles


You can always have multiple means of access. For instance, use SSH tunnels for the Desktop App, and use SSL/TLS (or whatever you decide on that is compatible/desirable) for the web version. Then again, you could use web ports and "web security" for the Desktop App, and have it play as a "web app". However, as Charles mentioned it's really hard to architect it without a clearer view of what exactly you're trying to accomplish.


Regards,
Michael

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>