Hi Oleg
There are provisions in the SessionRequest impl code that ensure
SessionRequestCallback will fire even if it is set after completion of
the request (successful or unsuccessful). However, since this question
pops up fairly regularly, I do have to admit this may be not obvious
without actually reading the javadocs. I was hesitant whether I should
make connect method take SessionRequestCallback as a parameter, as I
generally tend to dislike methods that take more than 3 parameters, but
in this case this seems justified. Fix coming.
thanks Oleg! Maybe you could have an overloaded method in addition, for
those of us who want to pass a SessionRequestCallback as well
regards
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
