[brlug-general] PHP help

[Dustin Puryear]

Yeah, I've done custom stuff for logging, but I'm getting a little tired 
of every solution being a little different. I'm starting to push for 
consistency whenever possible (e.g., using log4X for PHP, perl, Java, 
etc), etc.

The audit isn't for table mods. I think we'll just use log4php for that 
with a custom configuration and $audit_log->info() everything.

Why PHP? Supportability. We may or may not end up supporting this, and 
it's just.. easier for people to find support for it than, say, C++, C#, 
Java, etc. I know of a decent sized project that got stopped dead in its 
tracks (another shop, not us) because they kept losing their Java 
resources to other projects. Too tight a resource pool in my opinion.

--
Dustin Puryear
President and Sr. Consultant
Puryear Information Technology, LLC
225-706-8414 x112
http://www.puryear-it.com

Author, "Best Practices for Managing Linux and UNIX Servers"
   http://www.puryear-it.com/pubs/linux-unix-best-practices/


worms wrote:
> For templating I'ved used Smarty a good bit ( about 4 years ago ) and
> the separation between code and html was great and you can do allot to
> customize smarty.
> However everyone now and then some real annoying bugs would pop up.
> 
> I've only done LDAP stuff in C# but if the php library is anything
> similar then shouldn't be too difficult to write your wrapper to
> provide the functionality you need ( binding to the directory,
> searching for objects, get/setting properties on objects, etc. )
> 
> For audit logging if you are talking about keeping a history of
> changes one approach it to create audit tables which mirror the schema
> of the tables you want to audit and use a trigger to copy the data
> into the audit tables before modifying the data.
> 
> For general logging I've always written my own basic loggers to
> accomplish  tracing, debugging output, application event logging (
> errors, warning, information ).
> 
> If I may ask, out of curiosity, what are the reasons for going with PHP ?
> 
> --Lance
> 
> On Thu, Apr 17, 2008 at 6:17 PM, Dustin Puryear <dustin at puryear-it.com> wrote:
>> Hey guys- We are looking at building a tool in PHP and we need some
>>  suggestions for the following modules/classes:
>>
>>  Logging. We need to be able to do general logging (e.g., debug logging,
>>  info logging). I've used log4php before (as well as log4perl and log4j),
>>  and it works well. Other suggestions?
>>
>>  Audit Logging. We COULD use log4php I suppose. Other ideas?
>>
>>  Access Rights. We need to manage access to a given page and elements
>>  within that page. We'll be doing this using LDAP groups. Best method? Is
>>  there an existing module out there to do this? We could do this using
>>  php-ldap ourselves, but I'm hoping there is already a wrapper for this
>>  that provides a more generic interface. Nothing as complicated as using
>>  SiteMinder or anything of course. :)
>>
>>  Templating. We will be using a templating system to separate code from
>>  the presentation. What have you used? Thoughts?
>>
>>  --
>>  Dustin Puryear
>>  President and Sr. Consultant
>>  Puryear Information Technology, LLC
>>  225-706-8414 x112
>>  http://www.puryear-it.com
>>
>>  Author, "Best Practices for Managing Linux and UNIX Servers"
>>    http://www.puryear-it.com/pubs/linux-unix-best-practices/
>>
>>  _______________________________________________
>>  General mailing list
>>  General at brlug.net
>>  http://mail.brlug.net/mailman/listinfo/general_brlug.net
>>
> 
> _______________________________________________
> General mailing list
> General at brlug.net
> http://mail.brlug.net/mailman/listinfo/general_brlug.net