I'm trying to come up with a good way to keep computers registered on a server. I have a SQL database where all the registrations will be saved. This is a server/client system of mine, and I want to make very sure that each client is uniquely registered on the server, they don't get duplicated, and so on. Basically, it's similar to a software activation system, but not quite so secure and strict. However, it does need to be strict enough to make sure every one computer has one registration.
I was just wondering if anyone had any input on the subject.
Now in the database, I have 1 table which holds all the clients. The way I plan on going about this is when the client connects to the server, the first thing the client does is sends its own registration ID to the server. I cannot rely on IP address or host name because those are subject to change. Therefore, I need my own unique ID. So if the client its self knows it's registered, and it knows its unique code, it will send along this code to the server. The server will recognize this code and validate it. If the client is not registered, it will send along a null value to the server, which the server will interpret as needing to register. So at that moment, the server will automatically create a new record in the database, along with a new unique code, and send that code back to the client. The client will from then on use that code when connecting to the server.
This can be interpreted as a Cookie - only cookies can change, they're unique to a session, not to the client. This is also not on the same level of login either - there's a separate login validation process. A different user can login through the same client, but the client always has this same code.
What I need help with is trying to figure out a nifty way to keep track of these clients - as Microsoft keeps track of their products (Windows, Office, SQL, etc.). I just don't need it as complex as a full fledged activation system.
JD Solutions
I was just wondering if anyone had any input on the subject.
Now in the database, I have 1 table which holds all the clients. The way I plan on going about this is when the client connects to the server, the first thing the client does is sends its own registration ID to the server. I cannot rely on IP address or host name because those are subject to change. Therefore, I need my own unique ID. So if the client its self knows it's registered, and it knows its unique code, it will send along this code to the server. The server will recognize this code and validate it. If the client is not registered, it will send along a null value to the server, which the server will interpret as needing to register. So at that moment, the server will automatically create a new record in the database, along with a new unique code, and send that code back to the client. The client will from then on use that code when connecting to the server.
This can be interpreted as a Cookie - only cookies can change, they're unique to a session, not to the client. This is also not on the same level of login either - there's a separate login validation process. A different user can login through the same client, but the client always has this same code.
What I need help with is trying to figure out a nifty way to keep track of these clients - as Microsoft keeps track of their products (Windows, Office, SQL, etc.). I just don't need it as complex as a full fledged activation system.
JD Solutions