That's an interesting idea, but I'm having trouble thinking it all the way through. Are you licensing simultaneous connections per host? Or simultaneous connections anywhere? Or endpoint-pairs? If it's endpoint-pairs, where do you store the license info? If it's simultaneous connections anywhere, I guess you'd need a central license server, which would be annoying for users. If it's simultaneous connections per host, then you have to license each host, which is roughly equivalent to licensing each user I guess.
I'd love to understand this because my product is all about 2 or more users using it together. - Stefan Reitshamer On Jan 11, 2010, at 10:29 AM, Scott Ribe wrote: > If users can effectively share logins, then you need to license per > connection. To keep it simple, just drop the per-user part. > > -- > Scott Ribe > [email protected] > http://www.killerbytes.com/ > (303) 722-0567 voice
