Re: [Beepcore-java-users] Requireing a profile

[Marshall R. <mr...@db...>]

> A note on tuning profiles, SASL is a tuning profile that affects the
session
> state, but does not issue a tuning reset.

actually, this is not true. if a security layer is negotiated as a part of
the SASL process, then a tuning reset will occur.


> The design decision we made was to leave this kind of thing out, because
it can
> be implemented in the profiles, there did not appear to be a general
solution,
> and perhaps the greatest consideration was that it adds a lot of
complexity to the
> wrapper.

in the C and Tcl implementations, each data exchange profile is responsible
for determining whether the tuning is to its liking or not.

in the Java implementation, one could (as bill points out), have a subclass
of Profile that does the checking for you, so that the profile itself
doesn't have to check. seems like a fairly straight-forward abstraction to
put together.

however, at the present time, beepcore-java doesn't have that abstraction.

/mtr