Hi,
This may sound like a 'blast from the past' but I had a similar need a
few years ago and the client agreed to run a SQLserver solution. We
supplied a licence for a number of simultaneous connections and as each
separate PC and Mac fired up our app it logged onto the central database
which kept count of the number running at the same time.
Our application was supplied with a central server based database which
all users needed access to in order to use our system. In those
customers with large networks and firewalls between segments, the
machines couldn't 'see' each other, but they had to be able to access
one server where all the output was filed.
We used the MAC address of each machine to distinguish individual
computers, which had a timer running to tell the server they were still
connected even when the operator was on a lunch break. When a machine
was switched off and failed to 'poll' for a given period, say 30
minutes, the machine count was decremented and that machine removed
>from the database list of active machines.
If the licensed number of machines was already running when another
machine tried to log in, its request was denied and the app put up a
screen message asking for another licnce to be added.
This approach was developed because our first client hated all
registration schemes and individual passwords. He wanted all his staff
to be able to work on any computer depending on where they were that day!
The client could email us for a new registration key to add another
machine to the list whenever he expanded his operation.
We subsequently used this approach by modifying the key to allow a 90
day demo system to be installed and evaluated. Then if the customer
wanted to keep the system we emailed a full licence key on receipt of
payment for the system.
HTH
Doug Neale
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|