First, I don't wanna to catch there exception, it's too slow. Let user
to modify it in connection string isn't good idea, it's used for
process identification, not for custom stuff - even Firebird tools are
not allowing to modify it.
On the other hand, I was thinking about, instead of showing stricly
process name - which is for ASP.NET almost useless, we may show the
path to current application. This may be helpful to see what site is
having what connection.
The only problem is, how to detect this in advance. I haven't looked
to it deeply yet, but maybe there's a way to detect ASP.NET
environment easily.
What do you think?
--
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
