Here is my almost-ready-for-production cut of the component. I'm pretty satisfied with this code. I have enough flexibility with the methods, yet still retain many default values, in the init() method, that I don't normally touch.
I do have to give a lot of thanks to the "power contributors" of this list. I have learned quite a bit about CFCs and OOP (as it applies to CFMX) from lurking here. Is this of the caliber to post on the cfczone or cflib sites? I haven't seen too many, if any, functions that handle LDAP queries. Do all udfs on cflib need to be built with cfscript only or will they also accept tag-based udfs? Thanks -----Original Message----- From: Nathan Dintenfass [mailto:[EMAIL PROTECTED] Sent: Saturday, August 09, 2003 8:07 PM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] Component Critique Wanted Looks good. One thing to consider for making it more flexible would be building an init() method that takes a list (or array) of servers and that login info, etc. and stores that as an instance variable (perhaps even using an addServer() method). That way this component will be abstracted from the specifics of your environment. You could then loop through the servers passed in, which would tighten up the code a bit. The only other comment is that you seem to use the Arguments. prefix on all your arguments except sortOrder. I'd also think that it might be nice to have a default SortOrder and Separator rather than needing to pass those in every time.
cfcActiveDirectoryService.cfc
Description: cfcActiveDirectoryService.cfc
