For people who saw Ryan Stewart's tutorial "getting started with AFCS" and are not receiving the Authentication Success event. The browser is caching the session therefore you cannot rely on the Authentication Success event as a hook for initializing your application. The first time you run the app it will work but successive attempts could result in a cached session being used. The app will hang waiting for the event that never comes. To avoid this either quit the browser between sessions OR use the ConnectSession or ConnectSessionContainer's SessionEvent.SYNCHRONIZATION_CHANGE and then check for the isSynchronized property. The isSynchronized property exists on all the manager classes so you can also check them depending on what part of the session you are trying to use.
