#1 TuningProfile.setNextProfileRegistry

[Dave Golombek]

There are many situations in which a BEEP peer may not
wish to advertise a set of profiles until after a
certain level of Authentication/Authorization has been
performed. Right now, there is no clean way to change
the ProfileRegistry as soon as a TuningProfile
successfully completes. Right now
TuningProfile.complete takes a a ProfileRegistry to
install for the newly negotiated Session, which
essentially is the same ProfileRegistry as was
installed for the last Session (TLSProfile removes
itself, but it's essentially the same). It would be
nice to have something like:

class TuningProfile .... {
private ProfileRegistry nextRegistry;

public void
TuningProfile.setNextProfileRegistry(ProfileRegistry
registry) {
nextRegistry = registry;
}

public void complete(Channel channel,
SessionCredential localCred,
SessionCredential peerCred,
Object argument) ... {
...
Session s = channel.getSession();
s.reset(localCred, peerCred, nextRegistry,
argument);
....
}
}

If I'm missing a clean way of doing this under the
current design, please let
me know. Thanks,

Dave