GetBestSlot is not a callback. It is a call to NSS to return the best slot for an operation. The application wants to OVERRIDE the NSS decision, and the application doesn't have control of WHEN the slot choice is made, so a callback is natural.
I still don't know why Andrew wants to override the "BestSlot" decision. Another way to do this might to be configure the slot capabilities... at this point I don't know how that can be done. -Tej Aleksey Sanin wrote: > There is already a NSS callback (GetBestSlot). Why the application > needs to > have another one??? Sorry, I don't see reasons for this. If NSS can > provide > the same functionality thru multiple "slots" then NSS should take care of > configuring which "slot" is used by application. I really don't like the > idea of > global callbacks. It sounds like a bad design to me. > > Aleksey > > >Application callbacks would be a good way. > >Whenenver the crypto code needs to determine a slot, it > >can invoke a callback, whose signature is similar to GetBestSlot. > >If the callback is not specified, it can just use GetBestSlot. > > > > > > > _______________________________________________ xmlsec mailing list [EMAIL PROTECTED] http://www.aleksey.com/mailman/listinfo/xmlsec
