We've been doing some testing of CompleteFTP and we like what we've seen so far. The plug-in architecture for .Net is very nicely designed and suits our needs particularly well, especially for events. Hooray!
One thing we've noticed in our testing is that the native CompleteFTP authentication appears to produce significantly better performance numbers in our stress test benchmarks than a custom authentication plugin, even when said plugin does no lookups, just returns true for authentication. Is this due to the plugin call overhead?
We tried writing directly to the CompleteFTP tables in the config.sdf file but the user we created wasn't active until the service was restarted, so we're assuming that the native authentication credentials are cached at startup and updated when "Apply Changes" is clicked in the admin tool. Is that the case?
We're looking for the most performant method of user authentication where we can manage the creation/update/deletion of users. It would seem that the authentication extension feature will let us maintain the users in our own database but at the cost of some performance. Can anyone confirm this hypothesis?
Thanks in advance,
Bob Mc.