Jia, the attribute sessionId is only stored in the client and server side. the PublicSID is never used to authenticate users, publicSID are send with every client-object to all users to have a unique hash to identify a user. A publicSID also never changes when you re-connect into a conference room.
So the sessionId is like the private session-hash to auth users while the publicSID is the public hash to make sure you have a unique string for each user Sebastian 2010/11/2 jia <412596...@qq.com> > hi ,Sebastian > sessionID is associated with user ,PublicSID is associated with > client Browser ; > Why need to use sessionID ? you can make PublicSID also be associated > with user . > Thank you! > > -- > You received this message because you are subscribed to the Google Groups > "OpenMeetings User" group. > To post to this group, send email to openmeetings-u...@googlegroups.com. > To unsubscribe from this group, send email to > openmeetings-user+unsubscr...@googlegroups.com<openmeetings-user%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/openmeetings-user?hl=en. > > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.wagner-sebastian.com seba.wag...@gmail.com -- You received this message because you are subscribed to the Google Groups "OpenMeetings User" group. To post to this group, send email to openmeetings-u...@googlegroups.com. To unsubscribe from this group, send email to openmeetings-user+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/openmeetings-user?hl=en.
