Subject | Re: [firebird-support] Limiting / Regulating Database Connections |
---|---|
Author | Alexandre Benson Smith |
Post date | 2006-03-22T05:46:35Z |
msimmons15 wrote:
I have not yet implemented such limits on my apps.
But if I would do it, I would use the ethernet MAC address, this is
garanted unique, if the user lost the connection, when it came back, the
system will identify it as the same user, so I see no problems with dead
clientes coming alive again.
What I intend to do is something like this:
1.) Has in some place a number of valid licenses
2.) each users who logs will create an entry in some table, with it's
MAC address, and machine name
3.) if all the licenses are used no new mac address should be added,
only trough an admin option the administrator could see the licenses
used, if he finds that one pair of machine/MAC Address is not used
anymore, it will delete that record, so a new machine could login into
4.) don't know, I think it should be sufficient, I wrote this from the
top of my head, can't remember if I considered any other
problem/exception to the above, but it could serve as a guideline for you.
To increase the security and to avoid the users tampering with the data,
you could store hashes of the values, or something similar. My actual
customers call me and say. "Hey I installed a new machine could you
please send me an invoice about this license ?" :-) So I am really not
worried about it right now.
HTH
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br
> Has anyone seen a better approach for regulating connections?Mike,
>
> Thanks,
> Mike Simmons
>
I have not yet implemented such limits on my apps.
But if I would do it, I would use the ethernet MAC address, this is
garanted unique, if the user lost the connection, when it came back, the
system will identify it as the same user, so I see no problems with dead
clientes coming alive again.
What I intend to do is something like this:
1.) Has in some place a number of valid licenses
2.) each users who logs will create an entry in some table, with it's
MAC address, and machine name
3.) if all the licenses are used no new mac address should be added,
only trough an admin option the administrator could see the licenses
used, if he finds that one pair of machine/MAC Address is not used
anymore, it will delete that record, so a new machine could login into
4.) don't know, I think it should be sufficient, I wrote this from the
top of my head, can't remember if I considered any other
problem/exception to the above, but it could serve as a guideline for you.
To increase the security and to avoid the users tampering with the data,
you could store hashes of the values, or something similar. My actual
customers call me and say. "Hey I installed a new machine could you
please send me an invoice about this license ?" :-) So I am really not
worried about it right now.
HTH
see you !
--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br