1984 (Big Brother)
in [General]
|
Prev: How to handle a submitted form with no changes -- bestpractices sought
Next: Counting Children!
From: viraj on 17 Sep 2010 23:44 > > Remind him that he must logout normally to lock the DB if you follow the thread closely, this is a requirement. boss may not logout properly :) that's why all suggest a mechanical ways for the job. pressure sensors, cameras etc etc ~viraj > > > > On Sep 12, 2010, at 12:37 PM, Joshua Kehn wrote: > >> Tedd- >> >> Would he consider access to another database? I.e. a separate, say memcached db which stores the "boss" status? >> >> An issue with the temporary file would also be session length, if the session expires without the user explicitly logging off, the file wouldn't be removed. A way to bypass this would be to add some sort of session expiration header to the file and update that. >> >> And couldn't you make a simple check if the boss is logged in or not by the ability to access the database? >> >> Regards, >> >> -Josh >> ____________________________________ >> Joshua Kehn | Josh.Kehn(a)gmail.com >> http://joshuakehn.com >> >> On Sep 12, 2010, at 12:32 PM, tedd wrote: >> >>> Hi gang: >>> >>> I have a client who wants his employees' access to their online business database restricted to only times when he is logged on. (Don't ask why) >>> >>> In other words, when the boss is not logged on, then his employees cannot access the business database in any fashion whatsoever including checking to see if the boss is logged on, or not. No access whatsoever! >>> >>> Normally, I would just set up a field in the database and have that set to "yes" or "no" as to if the employees could access the database, or not. But in this case, the boss does not want even that type of access to the database permitted. Repeat -- No access whatsoever! >>> >>> I was thinking of the boss' script writing to a file that accomplished the "yes" or "no" thing, but if the boss did not log off properly then the file would remain in the "yes" state allowing employees undesired access. That would not be acceptable. >>> >>> So, what methods would you suggest? >>> >>> Cheers, >>> >>> tedd >>> >>> -- >>> ------- >>> http://sperling.com/ >>> >>> -- >>> PHP General Mailing List (http://www.php.net/) >>> To unsubscribe, visit: http://www.php.net/unsub.php >>> >> >> >> -- >> PHP General Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php >> > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >
From: TR Shaw on 18 Sep 2010 08:03 If you mean "not logoff properly" as, for instance, getting up and leaving his office for the day without logging off you can run a script when the machine "sleeps" or the screen saver runs and runs again when the machine transitions back to run. If your talking about powering off, same scripting approach as above (or just put DB on Boss' machine and if its off or crashes access ceases. As a crazy approach, put the DB on a thumb drive and attach the thumb to the Boss' car or house keys. He plugs the thumb in when he wants to "grant" access and takes it when he leaves because he need his keys. On Sep 17, 2010, at 11:44 PM, viraj wrote: >> >> Remind him that he must logout normally to lock the DB > > if you follow the thread closely, this is a requirement. boss may not > logout properly :) > > that's why all suggest a mechanical ways for the job. pressure > sensors, cameras etc etc > > ~viraj > >> >> >> >> On Sep 12, 2010, at 12:37 PM, Joshua Kehn wrote: >> >>> Tedd- >>> >>> Would he consider access to another database? I.e. a separate, say memcached db which stores the "boss" status? >>> >>> An issue with the temporary file would also be session length, if the session expires without the user explicitly logging off, the file wouldn't be removed. A way to bypass this would be to add some sort of session expiration header to the file and update that. >>> >>> And couldn't you make a simple check if the boss is logged in or not by the ability to access the database? >>> >>> Regards, >>> >>> -Josh >>> ____________________________________ >>> Joshua Kehn | Josh.Kehn(a)gmail.com >>> http://joshuakehn.com >>> >>> On Sep 12, 2010, at 12:32 PM, tedd wrote: >>> >>>> Hi gang: >>>> >>>> I have a client who wants his employees' access to their online business database restricted to only times when he is logged on. (Don't ask why) >>>> >>>> In other words, when the boss is not logged on, then his employees cannot access the business database in any fashion whatsoever including checking to see if the boss is logged on, or not. No access whatsoever! >>>> >>>> Normally, I would just set up a field in the database and have that set to "yes" or "no" as to if the employees could access the database, or not. But in this case, the boss does not want even that type of access to the database permitted. Repeat -- No access whatsoever! >>>> >>>> I was thinking of the boss' script writing to a file that accomplished the "yes" or "no" thing, but if the boss did not log off properly then the file would remain in the "yes" state allowing employees undesired access. That would not be acceptable. >>>> >>>> So, what methods would you suggest? >>>> >>>> Cheers, >>>> >>>> tedd >>>> >>>> -- >>>> ------- >>>> http://sperling.com/ >>>> >>>> -- >>>> PHP General Mailing List (http://www.php.net/) >>>> To unsubscribe, visit: http://www.php.net/unsub.php >>>> >>> >>> >>> -- >>> PHP General Mailing List (http://www.php.net/) >>> To unsubscribe, visit: http://www.php.net/unsub.php >>> >> >> >> -- >> PHP General Mailing List (http://www.php.net/) >> To unsubscribe, visit: http://www.php.net/unsub.php >> >> > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php >
From: chris h on 18 Sep 2010 12:03 So whenever the boss is in a meeting and his screen saver kicks on then the business shuts down. Also I think we've established that thumbdrive + database = disaster. Maybe a thumbdrive that has file with some random hash. Then create a cron that checks for the existence of that file each minute. When the boss leaves the cron doesn't find the file and shuts down the DB, when the boss comes in the cron will see it and starts it up. But Tedd, I'm still thinking that a "dead man's switch" is the way to go. :) Chris. On Sat, Sep 18, 2010 at 8:03 AM, TR Shaw <tshaw(a)oitc.com> wrote: > If you mean "not logoff properly" as, for instance, getting up and leaving > his office for the day without logging off you can run a script when the > machine "sleeps" or the screen saver runs and runs again when the machine > transitions back to run. > > If your talking about powering off, same scripting approach as above (or > just put DB on Boss' machine and if its off or crashes access ceases. > > As a crazy approach, put the DB on a thumb drive and attach the thumb to > the Boss' car or house keys. He plugs the thumb in when he wants to "grant" > access and takes it when he leaves because he need his keys. > > On Sep 17, 2010, at 11:44 PM, viraj wrote: > > >> > >> Remind him that he must logout normally to lock the DB > > > > if you follow the thread closely, this is a requirement. boss may not > > logout properly :) > > > > that's why all suggest a mechanical ways for the job. pressure > > sensors, cameras etc etc > > > > ~viraj > > > >> > >> > >> > >> On Sep 12, 2010, at 12:37 PM, Joshua Kehn wrote: > >> > >>> Tedd- > >>> > >>> Would he consider access to another database? I.e. a separate, say > memcached db which stores the "boss" status? > >>> > >>> An issue with the temporary file would also be session length, if the > session expires without the user explicitly logging off, the file wouldn't > be removed. A way to bypass this would be to add some sort of session > expiration header to the file and update that. > >>> > >>> And couldn't you make a simple check if the boss is logged in or not by > the ability to access the database? > >>> > >>> Regards, > >>> > >>> -Josh > >>> ____________________________________ > >>> Joshua Kehn | Josh.Kehn(a)gmail.com > >>> http://joshuakehn.com > >>> > >>> On Sep 12, 2010, at 12:32 PM, tedd wrote: > >>> > >>>> Hi gang: > >>>> > >>>> I have a client who wants his employees' access to their online > business database restricted to only times when he is logged on. (Don't ask > why) > >>>> > >>>> In other words, when the boss is not logged on, then his employees > cannot access the business database in any fashion whatsoever including > checking to see if the boss is logged on, or not. No access whatsoever! > >>>> > >>>> Normally, I would just set up a field in the database and have that > set to "yes" or "no" as to if the employees could access the database, or > not. But in this case, the boss does not want even that type of access to > the database permitted. Repeat -- No access whatsoever! > >>>> > >>>> I was thinking of the boss' script writing to a file that accomplished > the "yes" or "no" thing, but if the boss did not log off properly then the > file would remain in the "yes" state allowing employees undesired access. > That would not be acceptable. > >>>> > >>>> So, what methods would you suggest? > >>>> > >>>> Cheers, > >>>> > >>>> tedd > >>>> > >>>> -- > >>>> ------- > >>>> http://sperling.com/ > >>>> > >>>> -- > >>>> PHP General Mailing List (http://www.php.net/) > >>>> To unsubscribe, visit: http://www.php.net/unsub.php > >>>> > >>> > >>> > >>> -- > >>> PHP General Mailing List (http://www.php.net/) > >>> To unsubscribe, visit: http://www.php.net/unsub.php > >>> > >> > >> > >> -- > >> PHP General Mailing List (http://www.php.net/) > >> To unsubscribe, visit: http://www.php.net/unsub.php > >> > >> > > > > -- > > PHP General Mailing List (http://www.php.net/) > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > >
From: tedd on 19 Sep 2010 09:32
At 12:03 PM -0400 9/18/10, chris h wrote: > >But Tedd, I'm still thinking that a "dead man's switch" is the way to go. > :) Chris et al: I think the method I'll recommend to the client is to have the entire office tied to his computer. When it's on, everything is up and when it's off, everything is down That way if the client wants to leave (lunch, bathroom, whatever), he can turn his computer off, or leave it on -- as he wants. If he doesn't show up for work (vacation, sick, whatever), he can tell a subordinate to turn his computer on, or not -- it's totally his choice. The beauty of this method is that it is very simple to understand. There's nothing complicated about it. As I tell my grand-kids "Half the people you meet everyday are below average intelligence -- plan for it". There's nothing elitist about my statement, but rather a statement of fact. I often over estimate the understanding of clients and as I get older I see the error in my ways. Program for excellence, but design for stupidity. Thanks to all. Cheers, tedd -- ------- http://sperling.com/ |