Hi, > is there a way to restrict the number of different connections to a > tcp server, or to prevent to login with the same username and password > from different IPs?
Currently not. What you could do is run a background thread and detect if there are too many open sessions (killing new sessions). But it would be a relatively ugly workaround. I will add a feature request for: "Listener or authentication module for new connections, or a way to restrict the number of different connections to a tcp server, or to prevent to login with the same username and password from different IPs. Possibly using the DatabaseEventListener API, or a new API.". However, I will not have time to implement it in the near future. Patches are welcome of course! But I guess first we need to discuss what the best solution would be. Regards, Thomas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
