Skip to main content

Spec Clarification: Recording API

1 reply [Last post]
Joined: 2010-09-21

Calling delete method on Recording request is throwing both ENTRY_STATE_CHANGED event first followed by ENTRY_DELETED event.

Also calling getState() method on recording request when ENTRY_STATE_CHANGED event is received (for delete operation) is giving IllegalStateException.

Is it justified to throw ENTRY_STATE_CHANGED event when delete is called since it also throwing ENTRY_DELETED event?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2008-12-18

I don't know if it's justified, but it's also not prohibited.
Feel free to file a bug on this if you like and we can look into addressing it for a future release.