Home >> All >> edu >> ou >> kmi >> buddyspace >> [ core Javadoc ]

• edu.ou.kmi.buddyspace.core: Javadoc index of package edu.ou.kmi.buddyspace.core.


Package Samples:

• edu.ou.kmi.buddyspace.core

Classes:

• BSConnectionBean: BSConnectionBean is the main bean for BuddySpaceBeans. A BSConnectionBean mantains connection to a jabber server. All the other beans are dependent on this and has to be reset (typically using bean. setConnection function) after a new connection is setablished ( BSConnectionBean.connect function). The class is based on ConnectionBean and implements ConnectionListener from JabberBeans .
• BSCore: BSCore is the main class of BuddySpace backend. It provides the jabber client functionality using other classes such as BSConnectionBean , BSMessengerBean , BSPresenceBean , BSInfoQueryBean and other specialized classes.
• BSInfoQueryBean: BSInfoQueryBean handles IQ part of jabber protocol. It relies on BSConnectionBean which provides actual connection. BSInfoQuery . setConnection function must be called after each connection establishment.
• BSLogger: BSLogger class logs sent and received packets through given connection and the connection state. To listen to logs register your BSLogListener by addLogListener .
• BSMessengerBean: BSMessengerBean provides message handling. It relies on BSConnectionBean , which must be set after each reconnection. It uses MessengerBean .
• BSPresencesOfJID: BSPresencesOfJID contains presence information about all resources the given JID is logged from. It includes list BSPresenceInfo records.
• BSRosterBean: BSRosterBean provides roster handling. It relies on BSInfoQueryBean , which must be set after each reconnection. It uses RosterBean .
• BSRegisterBean: BSRegisterBean provides new account registration handling. It relies on BSInfoQueryBean , which must be set after each reconnection.
• BSAgentsBean: BSAgentsBean provides agents functionality handling. It relies on BSInfoQueryBean , which must be set after each reconnection.
• BSAuthorizationBean: BSAuthorizationBean provides athentication handling. It relies on BSInfoQueryBean , which must be set after each reconnection.
• BSPresenceBean: BSPresenceBean provides presence handling. It relies on BSConnectionBean , which must be set after each reconnection.
• BSMessageAdapter: BSMessageAdapter empty implementation of BSMessageListener interface providing message events notifications.
• BSPresenceAdapter: BSPresenceAdapter empty implementation of BSPresenceListener interface for presence changes notifications.
• BSPresenceInfo: BSPresenceInfo contains presence information. It includes JID , availability, show and status information.
• BSAuthEvent: BSAuthEvent contains information about event during authentication process. It contains new current state.
• BSLoginListener: BSLoginListener is interface you can implement to get login events notifications from BSCore.
• BSAuthListener: BSAuthListener is interface you can implement to get authentication events notifications.
• BSPresenceListener: BSPresenceListener is interface you can implement to get presence changes notifications.
• BSRegListener: BSRegListener is interface you can implement to get registration events notifications.
• BSMessageListener: BSMessageListener is interface you can implement to get message events notifications.
• BSIQListener: BSIQListener is interface you can implement to get special iq events notifications.
• BSAgentsListener: BSAgentsListener is interface you can implement to get agents events notifications.
• BSAuthState: BSAuthState contains information about current phase of authentication process.
• BSRegState: BSRegState contains information about current phase of registration process.
• BSServedIDs: BSServedIDs provides storing of currently served PacketIDs.

Home | Contact Us | Privacy Policy | Terms of Service