You can't have it both ways pion. Either a user module would need to have a constantly updating local copy of the shared state (which is doable today) or it would need to consult a 3rd party like a database or master to get the info at the time of the request (not currently possible for logins). Since it's possible to keep ioftpd sync'd with the existing site admin commands the only functionality I see missing is the non-sync'd approached which is what I presume you were looking for. The idea of a pre-login event where you could issue ftp commands to create/rename/modify/validate users would appear to solve that.
The problem of which server to sync to is left to the reader. I've worked with distributed systems for a very long time and there is no single right answer. Whatever method would have been used by a module could be used by the event. You could even run an existing module standalone and then use the ioFTPD events to simply communicate with it that way.
|