Greg.Tillman wrote:I would be curious to know how many activations you think you would need so that licensing does not get in your way too often?
@Greg.Tillman Typically, I work on ~5 different projects per year. For some of these projects, there's a need to test on different environments.
I also have 2 physical machines (laptop + desktop)
So I would say I need my personal Reflector license to be active on 12 different machines within a year. Or, maybe 5 different machines within a month (since I'll be working at most on 2 different projects within the same month).
Another case is when I'm debugging a problem at a customer's site or on a QA or production server. For this case, it could be useful to have a temporary "floating" license that I can carry on a USB key. For that case, a single license that can be moved between computers (but never used concurrently on multiple computers) would be enough.
Now, there's also the issue of limited connectivity (for example when working on a VPN) that would prevent reflector from contacting an activation server.
The solution I would see for that would be to:
- For licenses that are meant to be active on multiple computers at once (all belonging to the same person), contact the activation server once every 2 weeks. If, within the last 2 weeks, the same license has been used to request activation on more than 5 different computers, deny the activation request. Otherwise, accept it.
This way, there's no need to continuously deactivate licenses on old VMs. I would only have to ensure the VM is connected to the Internet once in a while.
- For the "floating" license, generate a one-time authorization key that only stays valid for 1 day. Have a way to send this one-time key by email (so I can receive it on my phone if I don't have internet access on the computer on which I need to use reflector)