I'm not sure what you are trying to do with the database but you should really look into using an AuthBy SQL cascaded after your AuthBy LDAP. The folks at Open Systems have done a great job in the module addressing the issues you have raised and it doesn't seem to make sense trying to rewrite it all.
You can reuse an existing database connection from an AuthBy SQL and the associated database access methods in your own hook if you want to and that will also deal with most of the issues you have listed. Search the mailing list archives on this topic and you will find some examples. I found this one from Hugh particularly enlightening: http://www.open.com.au/archives/radiator/2000-06/msg00023.html As far as performance the limiting factor is usually the response time of your database queries and not Radiator itself. You can always run multiple instances of Radiator to spread the load and improve response time. Why not post your config file with a more detailed explanation of what you are trying to accomplish? A number of folks on the list are authenticating with LDAP/SQL combinations. You can also search the mailing list archives for examples of what others have done. Frank Danielson [Infrastructure Architect] voice:407.515.8633 fax:407.515.9001 ClearSky Mobile Media, Inc. 56 E. Pine St. Suite 200 Orlando, FL 32801 USA -----Original Message----- From: John McFadden [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 09, 2003 11:47 AM To: [EMAIL PROTECTED] Subject: (RADIATOR) Use of Oracle in PostAuthHook? We use LDAP to do the basic userid/password authentication but intend to use one or more Oracle databases to apply business rules as LDAP is not dynamic enough. The PostAuthHook gives us a place to do that but I'm not sure if I should try to do it within Radiator or via an external program call. I'm a bit nervious about the Radiator/Perl SQL overhead. Does the PostAuthHook require a new connection for each request or for each session or each user? Or can I open the connection in a StartupHook (global var) then just share it in the PostAuthHook to do the required SQL query. Since we're just doing queries I'm hoping to share one connection to minimize overhead. Any issues with concurrency if we do? How do I detect the database is down and attempt to allocate a new connection? Comments, suggestions? Regards JLM === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message. === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.