On 06/06/2016 01:04 PM, Dimitry Sibiryakov wrote: > 06.06.2016 11:57, Alex Peshkoff wrote: >>> May be it worth not to send plugin >>>> name back at all if no plugin switch happen?.. >>>> >> Do you want to hide or fix a problem? > I want to prevent problem when client is switching to other plugin while > server don't > expect that. >
In that case we should choose one of two approaches: 1. Force windows (for posix it's unavoidable requirement) admins to type characters in plugin names in exact case and do not break that case-sensitive form later in the code. 2. Use case-insensitive comparison for data, coming from network. (must say that keeping strings in initial case in the code is IMO anyway good idea) I prefer second solution cause it looks much better for users. I do not believe in such BIG number of plugins that use of names that differ only in a case really makes sense. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
