On 11 Jan 2010, at 16:10, Stefan Reitshamer wrote: > 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.
It is possible that I don't know what I am talking about but this is my take on this. My app has a client server architecture. Each machine generally runs an instance of both the client component and the server component. A licence contains two counts. 1. User Seat count - U 2. Connection count - C CLIENT The client connects to all available server instances. Once the number of connected server instances exceeds the clients C limit it refuses to send execute requests to that server. Users however can still browse the server's resources. Authenticated users can still perform edits. SERVER All requests from the client include keyed licence data which defines U. The server examines the licence and allows a maximum of U connections from clients using that licence. There is no centralised licence server. A standard licence has say U = 2, C = 5. This means that each server will accept execute request from any two clients. Any client can send execute requests to up to 5 servers. This allows 1 user to fully utilise and administer the 5 servers for their individual benefit. However, if five users need to be able to execute requests on any one/ or more servers then 5 user licences will be required. To me this means that I can give offer wider access to my standard licence buyer (at home with his LAN) and still assert that individual human users need a licence. Regards Jonathan > - 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 > > > > ------------------------------------ > > MacSB email guidelines: http://tinyurl.com/2g55d6 > Use MacSB-Talk for off topic messages: > http://groups.google.com/group/macsb-talk > Yahoo! Groups Links > > >
