AW: [iaik-jce] SessionManager

["Dieter Bratko" <Dieter.Bratko@iaik.at>]

Hello,

By default iSaSiLk uses the DefaultSessionManager for session caching,
except when disablibing session cahcing (setSessionManager(null)) or
installing your own SessionManager -- either for a specific context:

sslContext.setSessionManager(mySessionManager);

or setting it as new DefaultSessionManager:

SessionManager.setDefault(mySessionManager);

Class SessionManager includes two abstract methods that have to be
implemented when writing your own SessionManager:

protected abstract void cacheSession(SSLTransport transport, Session
session);
protected abstract Session getSession(SSLTransport transport, Object
sessionID);

during the handshake procedure called from iSaSiLk´s -- not public --
Handshaker classes to put respectively get Session-Objects into (from) the
Session cache.

Regards,
Dieter Bratko

-----Ursprüngliche Nachricht-----
Von: iaik-jce-owner@iaik.tu-graz.ac.at
[mailto:iaik-jce-owner@iaik.tu-graz.ac.at]Im Auftrag von Andr‚ Benvenuti
Gesendet: Mittwoch, 12. Juli 2000 09:57
An: iaik help desk
Betreff: [iaik-jce] SessionManager


Hi,

A few questions abaout SessionManager:

- must a session manager must be explicitely set in a SSLContext
  to have one in use or is DefaultSessionManager per default set?

- who call the SessionManager methods (some are  commented as
  "For internal use")? Is it the socket constructor, who looks at the
SSLContext
  for any SesionManager?

Thanks in advance, Andre



--
Mailinglist-archive at
http://jcewww.iaik.at/mailarchive/iaik-jce/jcethreads.html

To unsubscribe send an email to listserv@iaik.at with the folowing content:
UNSUBSCRIBE iaik-jce

smime.p7s