Subject | Re: [IBO] Survey: TIB_Connection and Passwords |
---|---|
Author | Nando Dessena |
Post date | 2001-08-10T18:24:49Z |
Jason,
I would like to add just one thing: any system that I will ever
implement for passing passwords to IB will rely on custom code, so
personally I don't really care much about how many different behaviours
the PasswordStorage will allow. If I'm not mistaken, it is going to be
used both at design time and at run time; in the latter case, a couple
of event handlers (or a reference property to hook to a user defined
object, or an interface, etc.) to implement completely custom behaviour
would be a nice and cheap addition.
Don't know if an additional value is required to indicate that one's
going custom; probably Geoff's psNone would do.
leg (poorly translated). ;-)
Ciao
--
____
_/\/ando
> What I am leaning towards at the moment is to deprecate thethen go for it.
> PasswordRemembered (to streamed public) and to put in its place the
> PasswordStorage property as suggested by Geoff. It's default behavior will
> be what everyone is used to in the past. I've looked over the changes and I
> don't think it is going to be too complex.
I would like to add just one thing: any system that I will ever
implement for passing passwords to IB will rely on custom code, so
personally I don't really care much about how many different behaviours
the PasswordStorage will allow. If I'm not mistaken, it is going to be
used both at design time and at run time; in the latter case, a couple
of event handlers (or a reference property to hook to a user defined
object, or an interface, etc.) to implement completely custom behaviour
would be a nice and cheap addition.
Don't know if an additional value is required to indicate that one's
going custom; probably Geoff's psNone would do.
> It also seemed to me that people favored the more complete approach.What would you expect? Give them a finger and they'll take an arm and a
leg (poorly translated). ;-)
Ciao
--
____
_/\/ando