I believe using a remote address is not at such a good idea. It's a (probably) easy-to-implement idea, but it has some drawbacks: It's easy to tweak this by hiding A4D behind a (software) load balancer or reverse proxy. The latter one is exactly what I do - for security reason.
I'd think about some kind of "licence cookie" on the client. Example: A4D could be licensed to "10 seats", where each seat has a short-term (let's say, one hour) cookie set. The server could keep track which license cookies are valid at a given time, issue new ones if there are cookie slots left, or deny the connection with a "license violation error" if a cookieless clients enters the field and the server already knows about 10 active browsers. If a client tries to tweak this by removing the cookie, he'd be a "new user" and receives a new cookie, using another license. I belive that this cookie-based licensing is flexible and not so easy to tweak, but I might be wrong. Sig -- Angaben gemäß §35a GmbH-Gesetz: ITServ GmbH Sitz der Gesellschaft: 55294 Bodenheim/Rhein Eingetragen unter Registernummer HRB 41668 beim Amtsgericht Mainz Vertretungsberechtiger Geschäftsführer: Peter Bauer, 55294 Bodenheim Umsatzsteuer-ID: DE182270475 _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
