Re: what is going on with gtk.php.net?

On Thu, 2004-07-22 at 21:29, Richard Thomas wrote: I > have annoying habit of thinking to far "beyond" the current need sometimes. a required trait for a good analyst programmer :) > How do you securely lock that down per employee? While you can create > per table and even field permissions in mysql you can't stop someone > from directly deleting records for another employee if all the records > are in the same table. When I implemented a shared address book for a company of 800 employees (web not gtk:(, and ldap as the backend ) Each record belonged to a user and you could only modify and delete your own records.There was a special case,records that belonged to the user 'company' These records were the global ones and only the designated administrator could modify them. > By using a tcp server and some authentication on connection you can > identify who is trying to talk to the system, Instead of letting the > clients submit querys they would submit datasets. By parsing and > building querys on the fly you can implement a per person level of > security. Even if someone did manage to connect to the server outside of > your client they could affect nothing more then they where allowed. Agreed. In my experience every commercial application has its trade offs between what the developer knows is the correct solution from every angle (security, failover etc) and what the company is prepared to spend both in cash and development time. While your arguments are correct, i think most of the companys i have worked for would not want to imlement such a bullet proof solution for somthing like an address book. But then again some might..... Are we getting just a little off topic here BTW? tony