Hi *,
looks like we have a kind of mismatch in best way to start trusted
auth (you can check the DNET-216 or similar thread here from last
month or so).
Now it's done like a lot of standard tools for FB. If you omit
username *and* password the trusted auth "started". Another option
will be using another true/false param in connection string with
priority. I wanna to hear your opinions *and arguments* on one of
these ways.
Also take into account, that the behavior should be consistent with
the "FB picture" and also across all supported engines in code
(managed, embedded, external). The trusted auth is done on server
sode, that means, even if you force it, server may not be configured
to use it. And of course it's supported *only for windows clients and
windows servers (if enabled)*.
Notes:
* Use arguments for code or behavior. Advantages and disadvantages.
* Argument is not, that you have to change something in your
connections string (and if you hardcoded it in code, that's your
fault, you should use app.config - sorry hard, but true) or code. 2.5
comes with other breaking changes, and you will probably need to
recompile your application anyway (and test it, of course).
* Keep thread topic!
--
Jiri {x2} Cincura (CTO x2develop.com)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Firebird-net-provider mailing list
Firebird-net-provider@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
