wimas3 - Project Hosting on Google Code

Last 30 days Nov 19, 2009 Roadmap (Where do we stand and what's the plan?) Wiki page commented on by ShawnCarnell - The capability parameter is a UUID. See http://dev.aol.com/aim/web/serverapi_reference#sendDataIM and http://dev.aol.com/aim/web/serverapi_reference#Capability It's a way for AIM clients to know that another client is actually capable of interpreting whatever kind of data you're sending. If you're building an app that is sending data that only your app can interpret, yes, you should generate a new UUID. There are bunch of ways to do that. http://en.wikipedia.org/wiki/Uuid If you're gonna be working with dataIMs that existing clients already support, you should use the same UUID as those apps. The capability parameter is a UUID. See http://dev.aol.com/aim/web/serverapi_reference#sendDataIM and http://dev.aol.com/aim/web/serverapi_reference#Capability It's a way for AIM clients to know that another client is actually capable of interpreting whatever kind of data you're sending. If you're building an app that is sending data that only your app can interpret, yes, you should generate a new UUID. There are bunch of ways to do that. http://en.wikipedia.org/wiki/Uuid If you're gonna be working with dataIMs that existing clients already support, you should use the same UUID as those apps. Earlier this year Nov 18, 2009 Roadmap (Where do we stand and what's the plan?) Wiki page commented on by lintoka123 - I couldn't find any documentation for sending dataIM. Can I have the details on the 4th parameter 'capability' of sendDataIM method? I couldn't find any documentation for sending dataIM. Can I have the details on the 4th parameter 'capability' of sendDataIM method? Sep 30, 2009 FAQ (Frequently Asked Questions) Wiki page commented on by DoctorWicked - I don't think "burgeoning" is the word you were looking for. Perhaps "fledgling"? Accurate, yet connoting potential. I don't think "burgeoning" is the word you were looking for. Perhaps "fledgling"? Accurate, yet connoting potential. Sep 02, 2009 QuickStartGuide (The quick 'n dirty way to get started writing a client with ...) Wiki page edited by DavidKotch - Revision r70 Edited wiki page through web user interface. Revision r70 Edited wiki page through web user interface. Jul 14, 2009 r69 (Ooops! Some lifestreaming code (unfinished) with custom depe...) committed by rsattar - Ooops! Some lifestreaming code (unfinished) with custom dependencies got checked in with wimas3 and wimas3_imserv. Apologies Ooops! Some lifestreaming code (unfinished) with custom dependencies got checked in with wimas3 and wimas3_imserv. Apologies Jul 13, 2009 r68 (* Currently unused, stores special contextual information ab...) committed by rsattar - * Currently unused, stores special contextual information about IMs meant for other uses, like IMServs, etc. * Currently unused, stores special contextual information about IMs meant for other uses, like IMServs, etc. Jul 13, 2009 r67 (* Disabled some code which is changing in the AIM host side,...) committed by rsattar - * Disabled some code which is changing in the AIM host side, and fixes compilation error against regular IM.as * Disabled some code which is changing in the AIM host side, and fixes compilation error against regular IM.as Jul 10, 2009 r66 (* Added new IMServSession class, which gives you a BUNCH of ...) committed by rsattar - * Added new IMServSession class, which gives you a BUNCH of new Transactions and Data types for creating/editing/removing/managing IMServs, which are persistent group chats in your BL (see http://blast.aim.com, or check out the latest AIM Express at http://www.aimexpress.com) * We decided to treat this as a separate project, so if you want group-chat functionality within your app, you can import wimas3_imserv, instead of wimas3. This way, wimas3 can remain free of all the extra weight of IMServ-only transactions/datatypes * Added new IMServSession class, which gives you a BUNCH of new Transactions and Data types for creating/editing/removing/managing IMServs, which are persistent group chats in your BL (see http://blast.aim.com, or check out the latest AIM Express at http://www.aimexpress.com) * We decided to treat this as a separate project, so if you want group-chat functionality within your app, you can import wimas3_imserv, instead of wimas3. This way, wimas3 can remain free of all the extra weight of IMServ-only transactions/datatypes Jul 10, 2009 r65 (* If you type 'ghost' as the buddy to add, it will add the b...) committed by rsattar - * If you type 'ghost' as the buddy to add, it will add the buddy but will not send you a BL event (this is something we have been seeing a lot in production, so it helps you debug your app) * Support for simulating 'sentIM' events. it will claim that you sent a random quote to 'buddy0' * Can turn 'echo' ims off. Just type 'echo [on\|off]' to the buddy. Default is on. * Tweaks to how many buddies/groups we show, and whether to show a group of ICQ users * Support for renameGroup/removeGroup transactions * Buddy icon urls are included in buddy presence info * Status messages are defaulted to a random google search of the buddy's SN * Fixed 602 simulation when sending an IM to a missing buddy * 'sendim' command now supports an optional 2nd param: 'sendim buddy4' will send an IM from the SN 'buddy4'. Good for testing unknown sender scenarios, or unread counts in other convo tabs * New 'go nuts' command which will send you a barrage of buddies going online/offline quickly. Good for testing how your BL code reacts to this. Turn off by typing 'go nuts-no-more' * Passing UIN '000000000' for an ICQ buddy will prevent them from having a validatedCellular in their mdir data * If you type 'ghost' as the buddy to add, it will add the buddy but will not send you a BL event (this is something we have been seeing a lot in production, so it helps you debug your app) * Support for simulating 'sentIM' events. it will claim that you sent a random quote to 'buddy0' * Can turn 'echo' ims off. Just type 'echo [on\|off]' to the buddy. Default is on. * Tweaks to how many buddies/groups we show, and whether to show a group of ICQ users * Support for renameGroup/removeGroup transactions * Buddy icon urls are included in buddy presence info * Status messages are defaulted to a random google search of the buddy's SN * Fixed 602 simulation when sending an IM to a missing buddy * 'sendim' command now supports an optional 2nd param: 'sendim buddy4' will send an IM from the SN 'buddy4'. Good for testing unknown sender scenarios, or unread counts in other convo tabs * New 'go nuts' command which will send you a barrage of buddies going online/offline quickly. Good for testing how your BL code reacts to this. Turn off by typing 'go nuts-no-more' * Passing UIN '000000000' for an ICQ buddy will prevent them from having a validatedCellular in their mdir data Jul 10, 2009 r64 (* Preliminary support for Lifestream API (more coming!) * Yo...) committed by rsattar - * Preliminary support for Lifestream API (more coming!) * You can now passing 'devId' during startSignedSession() to change it (if you signed off and wanted to sign in with a different devId) * Session will request '&rawMsg=1' to receive raw IM data with IM events * Preliminary support for Lifestream API (more coming!) * You can now passing 'devId' during startSignedSession() to change it (if you signed off and wanted to sign in with a different devId) * Session will request '&rawMsg=1' to receive raw IM data with IM events Jul 10, 2009 r63 (* Make SMSInfo return ints, because apparently we can receiv...) committed by rsattar - * Make SMSInfo return ints, because apparently we can receive negative values if there is an error on the SMS gateway * Make SMSInfo return ints, because apparently we can receive negative values if there is an error on the SMS gateway Jul 10, 2009 r62 (* Better parsing of IM data (we know when its 'incoming') * ...) committed by rsattar - * Better parsing of IM data (we know when its 'incoming') * Added 'isArchivedMessage' to IM * Added 'IMRawMessageData', which provides raw bytes of message for handling different langs, etc * Better parsing of IM data (we know when its 'incoming') * Added 'isArchivedMessage' to IM * Added 'IMRawMessageData', which provides raw bytes of message for handling different langs, etc Jul 10, 2009 r61 (* Support for 'imserv' userType) committed by rsattar - * Support for 'imserv' userType * Support for 'imserv' userType Jul 10, 2009 r60 (* Use centralized ResultLoader.encodeStrPart) committed by rsattar - * Use centralized ResultLoader.encodeStrPart * Use centralized ResultLoader.encodeStrPart Jul 10, 2009 r59 (* Added RenameGroup transaction * Added RemoveGroup transact...) committed by rsattar - * Added RenameGroup transaction * Added RemoveGroup transaction * Added RenameGroup transaction * Added RemoveGroup transaction Jul 10, 2009 r58 (* Added GROUP_ADDING event * Added GROUP_REMOVING event * Ad...) committed by rsattar - * Added GROUP_ADDING event * Added GROUP_REMOVING event * Added GROUP_RENAMING event * Added GROUP_RENAME_RESULT event * Added optional "context" object to BuddyListEvent * Updated RemoveBuddy, GetPresence, AddBuddy to support optional context in BuddyListEvent * Added GROUP_ADDING event * Added GROUP_REMOVING event * Added GROUP_RENAMING event * Added GROUP_RENAME_RESULT event * Added optional "context" object to BuddyListEvent * Updated RemoveBuddy, GetPresence, AddBuddy to support optional context in BuddyListEvent Jul 10, 2009 r57 (* Support for a 'smart' numerical property in Group) committed by rsattar - * Support for a 'smart' numerical property in Group * Support for a 'smart' numerical property in Group Jul 10, 2009 r56 (* Added support for "IM_SENT" fetch event. You are notified ...) committed by rsattar - * Added support for "IM_SENT" fetch event. You are notified when another WIM-based client signed in with the same identity as you sends an IM. * Support for "sentIM" and "lifestream" fetch event types * Added LifestreamEvent (incomplete) * Added support for "IM_SENT" fetch event. You are notified when another WIM-based client signed in with the same identity as you sends an IM. * Support for "sentIM" and "lifestream" fetch event types * Added LifestreamEvent (incomplete) Jul 10, 2009 r55 (* Added new base class, TransactionEvent, which provides bas...) committed by rsattar - * Added new base class, TransactionEvent, which provides basic statusCode information, and context info * Added new base class, TransactionEvent, which provides basic statusCode information, and context info Jul 10, 2009 r54 (* Fixed a stupid testing bug in SetPermitDeny * Use centrali...) committed by rsattar - * Fixed a stupid testing bug in SetPermitDeny * Use centralized encodeStrPart() * Fixed a stupid testing bug in SetPermitDeny * Use centralized encodeStrPart() Jul 10, 2009 r53 (* Transaction class has centralized signature creation (sigs...) committed by rsattar - * Transaction class has centralized signature creation (sigsha256) * Transaction class has centralized signature creation (sigsha256) Jul 10, 2009 r52 (* Turned off a bunch of logging * Support for Error 3013 - S...) committed by rsattar - * Turned off a bunch of logging * Support for Error 3013 - SecurId Next Token Required (AOL internal employee support) * Support for 3019 - Account Not allowed (parentally controlled accounts) * Use centralized ResultLoader.encodeStrPart() * Support for encoding a string into Base64 * Turned off a bunch of logging * Support for Error 3013 - SecurId Next Token Required (AOL internal employee support) * Support for 3019 - Account Not allowed (parentally controlled accounts) * Use centralized ResultLoader.encodeStrPart() * Support for encoding a string into Base64 Jul 10, 2009 r51 (* Created centralized encodeStrPart() because it is being us...) committed by rsattar - * Created centralized encodeStrPart() because it is being used all over the wimas3 source code * Created centralized encodeStrPart() because it is being used all over the wimas3 source code Apr 25, 2009 issue 3 (WIMAS3 wont function in web applications) commented on by rsattar - It sounds like you might have registered to wrong devID parameters. By default the devID parameters are "referer" based, in that it checks which site it is coming from before AIM allows you to log in. When you registered your key, did you make sure to unchecked "referer check" and make sure "client login" was checked? http://developer.aim.com/wimReg.jsp It sounds like you might have registered to wrong devID parameters. By default the devID parameters are "referer" based, in that it checks which site it is coming from before AIM allows you to log in. When you registered your key, did you make sure to unchecked "referer check" and make sure "client login" was checked? http://developer.aim.com/wimReg.jsp Older Nov 14, 2008 r50 (* Remove redundant Version.as file under openauth/) committed by rsattar - * Remove redundant Version.as file under openauth/ * Remove redundant Version.as file under openauth/ Nov 14, 2008 r49 (* Refactored logging.* and ResultLoader out to a "common" pr...) committed by rsattar - * Refactored logging.* and ResultLoader out to a "common" project (common.swc) * Refactored openauth.* out to "openauth" project (openauth.swc) * Changes to wimas3 and wimas3_mock_server to support the new class locations * Refactored logging.* and ResultLoader out to a "common" project (common.swc) * Refactored openauth.* out to "openauth" project (openauth.swc) * Changes to wimas3 and wimas3_mock_server to support the new class locations Nov 14, 2008 r48 (* Fix anonymous sessions * Fixed issue of not URI-Encoding t...) committed by rsattar - * Fix anonymous sessions * Fixed issue of not URI-Encoding the ids during setPermitDeny (i.e. +cellphonenum should be %2Bcellphonenum) * Minor code / comment cleanup * Fix anonymous sessions * Fixed issue of not URI-Encoding the ids during setPermitDeny (i.e. +cellphonenum should be %2Bcellphonenum) * Minor code / comment cleanup Nov 12, 2008 r47 (Big update to latest (11/11/08) in our internal repository: ...) committed by rsattar - Big update to latest (11/11/08) in our internal repository: wimas3 Changes --------------------- - ClientLogin: Listen for SecurityErrors, in case there is a problem with accessing crossdomain.xml - This can be caused by making a request while disconnected from the network - Support for getSMSInfo call (International numbers only right now) - Added 'statusDetailCode' to ResultData object - Added support for a "not allowed" mode for ClientLogin in case the account is parentally blocked - Support for "Blocked" and "Unknown" PresenceStates - "blocked" is actually not a real presence state, but it is useful to represent a state as "blocked" for users which are blocked (you are not supposed to see their state) - "unknown" state is actually used by ICQ for when you have added a buddy, but they have not yet added you (and shared their status with you) - Support in User object for: - 'smsNumber' property, which is extracted from the buddy attributes server - 'nonBuddy' property, which is true if the user is an ICQ added "phone number" contact - Use host-supplied 'userType' if it is supplied, otherwise we guess the userType as we did before - Changes/Additions to various Events: - New set of AttributeEvents, for buddy attribute get/set events - New set of SMSInfoEvents, for getSMSInfo requests - New event "userAuthorizationRequestResult" in UserAuthorizationEvent - BuddyListEvent now exposes the statusCode - Support for error subCodes and subCodeReasons in IMEvents - New MemberDirectoryEvent "directorySearchIOError" - Changes to Session.as: - Support for setBuddyAttribute/getBuddyAttribute - Support for getPermitDeny - Support for getSMSInfo (ICQ numbers only) - Support for requestAuthorization (ICQ Only) - Handles SecurityError events generated from ClientLogin - Upgrades to reconnection logic (more reliable, less 'eager') - Support for getting a client2Web authorization, which allows your user to be authenticated to AOL sites following a successful login - We now do the startSession call in XML instead of AMF3 - Support for requestBuddyList - Changes to various transactions: - AddBuddy will return a RESULT call which includes the statusCode, instead of just responding on a statusCode = 200 - Handle IOError's in GetMemberDirectory - Support for retrieving a BuddyList using GetPresence - Basic ResultLoader class will correctly close() a connection on a synthesized onTimeoutExceeded() - Force a max results of SearchMemberDirectory to 50 - SMSInfo support in SendIM and SendIMXML - Following host-side fixes, SetState and SetStatus no longer dispatch "MyInfo" events - Transaction class now supports building signed requests and supports optional timeout parameter Mock Server Changes -------------------- - Added 'set status [msg]' - Added 'clear status' - Support for simulating setBuddyAttribute/getBuddyAttribute - Support for (ICQ Only) getSMSInfo call - Support for getPermitDeny - Default fetch request timeout for Mock Session is 7 seconds instead of 30 wimas3 Test Client -------------------- - Support for testing get/setBuddyAttribute - Support for testing getMemberDir Big update to latest (11/11/08) in our internal repository: wimas3 Changes --------------------- - ClientLogin: Listen for SecurityErrors, in case there is a problem with accessing crossdomain.xml - This can be caused by making a request while disconnected from the network - Support for getSMSInfo call (International numbers only right now) - Added 'statusDetailCode' to ResultData object - Added support for a "not allowed" mode for ClientLogin in case the account is parentally blocked - Support for "Blocked" and "Unknown" PresenceStates - "blocked" is actually not a real presence state, but it is useful to represent a state as "blocked" for users which are blocked (you are not supposed to see their state) - "unknown" state is actually used by ICQ for when you have added a buddy, but they have not yet added you (and shared their status with you) - Support in User object for: - 'smsNumber' property, which is extracted from the buddy attributes server - 'nonBuddy' property, which is true if the user is an ICQ added "phone number" contact - Use host-supplied 'userType' if it is supplied, otherwise we guess the userType as we did before - Changes/Additions to various Events: - New set of AttributeEvents, for buddy attribute get/set events - New set of SMSInfoEvents, for getSMSInfo requests - New event "userAuthorizationRequestResult" in UserAuthorizationEvent - BuddyListEvent now exposes the statusCode - Support for error subCodes and subCodeReasons in IMEvents - New MemberDirectoryEvent "directorySearchIOError" - Changes to Session.as: - Support for setBuddyAttribute/getBuddyAttribute - Support for getPermitDeny - Support for getSMSInfo (ICQ numbers only) - Support for requestAuthorization (ICQ Only) - Handles SecurityError events generated from ClientLogin - Upgrades to reconnection logic (more reliable, less 'eager') - Support for getting a client2Web authorization, which allows your user to be authenticated to AOL sites following a successful login - We now do the startSession call in XML instead of AMF3 - Support for requestBuddyList - Changes to various transactions: - AddBuddy will return a RESULT call which includes the statusCode, instead of just responding on a statusCode = 200 - Handle IOError's in GetMemberDirectory - Support for retrieving a BuddyList using GetPresence - Basic ResultLoader class will correctly close() a connection on a synthesized onTimeoutExceeded() - Force a max results of SearchMemberDirectory to 50 - SMSInfo support in SendIM and SendIMXML - Following host-side fixes, SetState and SetStatus no longer dispatch "MyInfo" events - Transaction class now supports building signed requests and supports optional timeout parameter Mock Server Changes -------------------- - Added 'set status [msg]' - Added 'clear status' - Support for simulating setBuddyAttribute/getBuddyAttribute - Support for (ICQ Only) getSMSInfo call - Support for getPermitDeny - Default fetch request timeout for Mock Session is 7 seconds instead of 30 wimas3 Test Client -------------------- - Support for testing get/setBuddyAttribute - Support for testing getMemberDir Oct 08, 2008 issue 3 (WIMAS3 wont function in web applications) commented on by burtonmodel - i agree there is some quiet serious error with the BuddyListEvent it needs to be taken care of... i agree there is some quiet serious error with the BuddyListEvent it needs to be taken care of... Aug 05, 2008 issue 3 (WIMAS3 wont function in web applications) reported by cbk_bo...@yahoo.com - What steps will reproduce the problem? 1. Publish flash as3 SWF What is the expected output? What do you see instead? Originally I thought that flash just wasn't exporting the WIMAS3 libraries, but I created a debugger that sh What version of the product are you using? On what operating system? Latest svn release of wimas3 Please provide any additional information below. When I run the code in Flash CS3 it functions perfectly and flaw less. the out put shows all my buddies, who's online, ect. When I put it on my test server nothing functions. I made it debug so it shows everything that would be in the output in the textarea. Here's the example: http://68.4.109.51:8503 Also heres the code to work with. Thank you. *Start Code* import flash.display.; import flash.events.; import flash.external.ExternalInterface; import com.aol.api.wim.Session; import com.aol.api.wim.events.UserEvent; import com.aol.api.wim.; stage.scaleMode = StageScaleMode.NO_SCALE; stage.align = StageAlign.TOP_LEFT; var devId:String = "(my dev id)"; var session:Session = new Session(this.stage, devId, "test client", ".1"); function login() { session.signOn("myaimid", "myaimpassword"); } login(); function log(item) { cuelog.text = cuelog.text+'\n'+item; } function onBLReceived(event:BuddyListEvent):void { trace(event.buddyList.groups[0].users[i].aimId.toString()) // and to log everything so it shows on the website log(event.buddyList.groups[0].users[i].aimId.toString()) } function onStateChange(event:SessionEvent):void { trace(session.sessionState.toString()) log(session.sessionState.toString()); } //events session.addEventListener(BuddyListEvent.LIST_RECEIVED, onBLReceived); session.addEventListener(SessionEvent.STATE_CHANGED, onStateChange); end code * (keep in mind the log function should show up on the page as anything that would be in a trace action) What steps will reproduce the problem? 1. Publish flash as3 SWF What is the expected output? What do you see instead? Originally I thought that flash just wasn't exporting the WIMAS3 libraries, but I created a debugger that sh What version of the product are you using? On what operating system? Latest svn release of wimas3 Please provide any additional information below. When I run the code in Flash CS3 it functions perfectly and flaw less. the out put shows all my buddies, who's online, ect. When I put it on my test server nothing functions. I made it debug so it shows everything that would be in the output in the textarea. Here's the example: http://68.4.109.51:8503 Also heres the code to work with. Thank you. *Start Code* import flash.display.; import flash.events.; import flash.external.ExternalInterface; import com.aol.api.wim.Session; import com.aol.api.wim.events.UserEvent; import com.aol.api.wim.; stage.scaleMode = StageScaleMode.NO_SCALE; stage.align = StageAlign.TOP_LEFT; var devId:String = "(my dev id)"; var session:Session = new Session(this.stage, devId, "test client", ".1"); function login() { session.signOn("myaimid", "myaimpassword"); } login(); function log(item) { cuelog.text = cuelog.text+'\n'+item; } function onBLReceived(event:BuddyListEvent):void { trace(event.buddyList.groups[0].users[i].aimId.toString()) // and to log everything so it shows on the website log(event.buddyList.groups[0].users[i].aimId.toString()) } function onStateChange(event:SessionEvent):void { trace(session.sessionState.toString()) log(session.sessionState.toString()); } //events session.addEventListener(BuddyListEvent.LIST_RECEIVED, onBLReceived); session.addEventListener(SessionEvent.STATE_CHANGED, onStateChange); end code * (keep in mind the log function should show up on the page as anything that would be in a trace action) Aug 01, 2008 r46 (First checkin of wimas3 Test Anonymous Client. This is a ref...) committed by rsattar - First checkin of wimas3 Test Anonymous Client. This is a reference application showing how to create an anonymous AIM session (Wimzi) if you have a valid appKey. You can get a wimzi appKey by visiting http://wimzi.aim.com First checkin of wimas3 Test Anonymous Client. This is a reference application showing how to create an anonymous AIM session (Wimzi) if you have a valid appKey. You can get a wimzi appKey by visiting http://wimzi.aim.com Aug 01, 2008 r45 (Added settable state, away message and status message contro...) committed by rsattar - Added settable state, away message and status message controls, fixing a compilation error in TestClientPanel_.as Added settable state, away message and status message controls, fixing a compilation error in TestClientPanel_.as Aug 01, 2008 r44 (The most significant feature is the support for anonymous se...) committed by rsattar - The most significant feature is the support for anonymous sessions (Wimzi). You can now use wimas3 to develop "badges" for blogs or social media sites (see http://wimzi.aim.com). Also added a GetPermitDeny transaction. The most significant feature is the support for anonymous sessions (Wimzi). You can now use wimas3 to develop "badges" for blogs or social media sites (see http://wimzi.aim.com). Also added a GetPermitDeny transaction. Jul 25, 2008 r43 (The biggest change in this update is to the reconnection log...) committed by ShawnCarnell - The biggest change in this update is to the reconnection logic. We think the old logic may have been too aggressive for the average internet connection. This is a highly recommended update. This update is a little advanced from what is being using in Beta 5 of AIM Express: http://beta.aol.com/projects.php?project=aimexpress7 The biggest change in this update is to the reconnection logic. We think the old logic may have been too aggressive for the average internet connection. This is a highly recommended update. This update is a little advanced from what is being using in Beta 5 of AIM Express: http://beta.aol.com/projects.php?project=aimexpress7 Jul 25, 2008 r42 (The biggest change in this update is to the reconnection log...) committed by ShawnCarnell - The biggest change in this update is to the reconnection logic. We think the old logic may have been too aggressive for the average internet connection. This is a highly recommended update. This update is a little advanced from what is being using in Beta 5 of AIM Express: http://beta.aol.com/projects.php?project=aimexpress7 The biggest change in this update is to the reconnection logic. We think the old logic may have been too aggressive for the average internet connection. This is a highly recommended update. This update is a little advanced from what is being using in Beta 5 of AIM Express: http://beta.aol.com/projects.php?project=aimexpress7

r47 (Big update to latest (11/11/08) in our internal repository: ...) committed by rsattar - Big update to latest (11/11/08) in our internal repository: wimas3 Changes --------------------- - ClientLogin: Listen for SecurityErrors, in case there is a problem with accessing crossdomain.xml - This can be caused by making a request while disconnected from the network - Support for getSMSInfo call (International numbers only right now) - Added 'statusDetailCode' to ResultData object - Added support for a "not allowed" mode for ClientLogin in case the account is parentally blocked - Support for "Blocked" and "Unknown" PresenceStates - "blocked" is actually not a real presence state, but it is useful to represent a state as "blocked" for users which are blocked (you are not supposed to see their state) - "unknown" state is actually used by ICQ for when you have added a buddy, but they have not yet added you (and shared their status with you) - Support in User object for: - 'smsNumber' property, which is extracted from the buddy attributes server - 'nonBuddy' property, which is true if the user is an ICQ added "phone number" contact - Use host-supplied 'userType' if it is supplied, otherwise we guess the userType as we did before - Changes/Additions to various Events: - New set of AttributeEvents, for buddy attribute get/set events - New set of SMSInfoEvents, for getSMSInfo requests - New event "userAuthorizationRequestResult" in UserAuthorizationEvent - BuddyListEvent now exposes the statusCode - Support for error subCodes and subCodeReasons in IMEvents - New MemberDirectoryEvent "directorySearchIOError" - Changes to Session.as: - Support for setBuddyAttribute/getBuddyAttribute - Support for getPermitDeny - Support for getSMSInfo (ICQ numbers only) - Support for requestAuthorization (ICQ Only) - Handles SecurityError events generated from ClientLogin - Upgrades to reconnection logic (more reliable, less 'eager') - Support for getting a client2Web authorization, which allows your user to be authenticated to AOL sites following a successful login - We now do the startSession call in XML instead of AMF3 - Support for requestBuddyList - Changes to various transactions: - AddBuddy will return a RESULT call which includes the statusCode, instead of just responding on a statusCode = 200 - Handle IOError's in GetMemberDirectory - Support for retrieving a BuddyList using GetPresence - Basic ResultLoader class will correctly close() a connection on a synthesized onTimeoutExceeded() - Force a max results of SearchMemberDirectory to 50 - SMSInfo support in SendIM and SendIMXML - Following host-side fixes, SetState and SetStatus no longer dispatch "MyInfo" events - Transaction class now supports building signed requests and supports optional timeout parameter Mock Server Changes -------------------- - Added 'set status [msg]' - Added 'clear status' - Support for simulating setBuddyAttribute/getBuddyAttribute - Support for (ICQ Only) getSMSInfo call - Support for getPermitDeny - Default fetch request timeout for Mock Session is 7 seconds instead of 30 wimas3 Test Client -------------------- - Support for testing get/setBuddyAttribute - Support for testing getMemberDir

Big update to latest (11/11/08) in our internal repository: wimas3 Changes --------------------- - ClientLogin: Listen for SecurityErrors, in case there is a problem with accessing crossdomain.xml - This can be caused by making a request while disconnected from the network - Support for getSMSInfo call (International numbers only right now) - Added 'statusDetailCode' to ResultData object - Added support for a "not allowed" mode for ClientLogin in case the account is parentally blocked - Support for "Blocked" and "Unknown" PresenceStates - "blocked" is actually not a real presence state, but it is useful to represent a state as "blocked" for users which are blocked (you are not supposed to see their state) - "unknown" state is actually used by ICQ for when you have added a buddy, but they have not yet added you (and shared their status with you) - Support in User object for: - 'smsNumber' property, which is extracted from the buddy attributes server - 'nonBuddy' property, which is true if the user is an ICQ added "phone number" contact - Use host-supplied 'userType' if it is supplied, otherwise we guess the userType as we did before - Changes/Additions to various Events: - New set of AttributeEvents, for buddy attribute get/set events - New set of SMSInfoEvents, for getSMSInfo requests - New event "userAuthorizationRequestResult" in UserAuthorizationEvent - BuddyListEvent now exposes the statusCode - Support for error subCodes and subCodeReasons in IMEvents - New MemberDirectoryEvent "directorySearchIOError" - Changes to Session.as: - Support for setBuddyAttribute/getBuddyAttribute - Support for getPermitDeny - Support for getSMSInfo (ICQ numbers only) - Support for requestAuthorization (ICQ Only) - Handles SecurityError events generated from ClientLogin - Upgrades to reconnection logic (more reliable, less 'eager') - Support for getting a client2Web authorization, which allows your user to be authenticated to AOL sites following a successful login - We now do the startSession call in XML instead of AMF3 - Support for requestBuddyList - Changes to various transactions: - AddBuddy will return a RESULT call which includes the statusCode, instead of just responding on a statusCode = 200 - Handle IOError's in GetMemberDirectory - Support for retrieving a BuddyList using GetPresence - Basic ResultLoader class will correctly close() a connection on a synthesized onTimeoutExceeded() - Force a max results of SearchMemberDirectory to 50 - SMSInfo support in SendIM and SendIMXML - Following host-side fixes, SetState and SetStatus no longer dispatch "MyInfo" events - Transaction class now supports building signed requests and supports optional timeout parameter Mock Server Changes -------------------- - Added 'set status [msg]' - Added 'clear status' - Support for simulating setBuddyAttribute/getBuddyAttribute - Support for (ICQ Only) getSMSInfo call - Support for getPermitDeny - Default fetch request timeout for Mock Session is 7 seconds instead of 30 wimas3 Test Client -------------------- - Support for testing get/setBuddyAttribute - Support for testing getMemberDir

Last 30 days

Earlier this year

Older