RE: API changes in upcoming MediaSense 8.5(3) release http://developer.cisco.com/c/message_boards/find_category?p_l_id=2629775&mbCategoryId=0 2013-05-19T02:24:51Z 2013-05-19T02:24:51Z Chris Yeo http://developer.cisco.com/c/message_boards/find_message?p_l_id=2629775&messageId=12486315 2013-02-28T17:35:12Z 2013-02-28T17:35:12Z

Rico, We have updated the zip file on CDN and addressed the missing js files. Sorry for the inconvenience.

Chris Yeo 2013-02-28T17:35:12Z Chris Yeo http://developer.cisco.com/c/message_boards/find_message?p_l_id=2629775&messageId=4479716 2011-09-15T04:13:25Z 2011-09-14T03:54:46Z

In addition to what Ken provided, there are 2 more additional changes in 8.5(3): [b]sessionId parameter no longer allowed with getSessions API[/b]. We have modified the getSessions API to now require the client to specify a time range within which the request will be applied. The purpose was to apply some constraint on the number of sessions that such a request would return. Including a sessionId parameter actually limits the number of sessions to one (or zero if not found), which makes the time range requirement extraneous. However, adding a rule by which time range would become optional if a sessionId was specified would have made the API unnecessarily complex, especially since an alternate API is available specifically for this type of request. As a result we have eliminated sessionId as an acceptable parameter on the getSessions API, and clients including this parameter will receive an error response. Recommendation: Convert all calls to getSessions which include a sessionId parameter into calls to getSessionBySessionId. ------------------------------------------ [b]Error response codes to change for some APIs[/b]. Several APIs currently return a 5xxx responseCode if the value requested is not found in the database. This is technically incorrect. 5xxx response codes are intended to indicate that the server encountered an internal error, but in these cases it is the client who issued an invalid request. In release 8.5(3) then, these APIs will return a 4xxx responseCode instead. The specific APIs affected are: - cancelJob - deleteJob - getJobById - getJobResult - getJobs - addSessionTag - deleteSessionTag - deleteSessions When these APIs return responseCode 5005, they will now instead return 4005. The response message, "Failure: Cannot find value in database." will remain the same. Recommendation: Examine your client code for comparisons against responseCode values in the 5xxx range, and make sure they operate propertly when the responseCode value becomes 4xxx instead.   ===============================   Chris Yeo, Product Manager, MediaSense

Chris Yeo 2011-09-14T03:54:46Z