Authentication client-server using message queues in c language

Question

Hi all ... I'm working on this project about how to develop authentication server that serves multiple clients at a time
the client gives the name and password as request and the server authenticates the request and returns the result ... ALL communications between client and server should use message queues techniques ...and i want it in c language ... Can u help me with the code ... appreciate it soo much ..

Answer 1

GregS & Amardeep : thank u ma friends i really appreciate your help ... this is a detailed description about My " Homework" .. but you can skip the "add " & " delete " functions they r preety easy i can do it my self but the other i'm having problem .. sorry for bothering :

I required to build an authentication server as follows The server handles three types of requests: register (add use), unregister (delete user), and authenticate. The server will use message queues for all kinds of communications between the server and the client.
A request for registering a user contains a user name and a password. When the server receives a registration request, it adds the user name and password to the file of user names. The server then returns a confirmation message to the requester of the form “User name X was registered successfully”. A request for unregistering a user also contains a user name and a password. When the server receives a request for unregistering a user, the server first authenticates the user and then deletes the user. If the authentication failed, the server returns to the requester a message of the form “Authentication Failed: wrong user name or password”. Otherwise, the server returns a message to the user of the form “User name X deleted successfully”. When the server receives a request for authentication, the server checks the user name and password against the users file. Similarly, the server returns a message to the user with the result. I.e., either “Authentication successful” or “Authentication failed: wrong user name or password”. The server needs to be able to handle multiple requests at a time by being multi-threaded. Since authentication requests are expected to be much more frequent than registering or unregistering requests, all registration requests are handled in one thread and all unregisteration requests are handled within another thread. Authentication requests however are handled each in its own thread.

Thanx a lot I owe you very big favor guys .. sorry again ...