Re: RDi from a remote connection

Here is my experience, fwiw.
1-I believe the license is to the user. You can use it as many places as you like but obviously you can be in only one place at a time.
2-The transition from SEU to RDi was, for me, gradual. One day it dawned that I had not used an SEU session for over a year.
3-RDi allows you two ways to work on your projects. One is to connect directly to the libraries on the i and make changes there directly. The other, which I prefer, is to have the source copied into my PC so I can work off-line, and then connect when I want to compile. Both work well. I have also worked on a team where the project was shared and used SVN. That worked fine, too, although it took me some getting used to it.
4-RDi is really great if you want to connect to more than one system.

all fwiw.

On 1/26/2015 9:36 AM, Mike Cunningham wrote:

What's the best way to use RDi when working remotely (like a home office)? As I try to move from SEU to RDi for development I find myself going back to "the old ways" because it is so much easier to do work using SEU from home over VPN and secure telnet. I am also not sure of the licensing rules for RDi vs the unlimited license I have for Client Access. Do I need to purchase another RDi license for home use? I would still VPN to work with RDi which I could then remote to my office desktop but that just adds another layer of complication. Is anyone doing this with RDi?

Thanks
Mike Cunningham