Issue 1954 in bigbluebutton: Example create call not idempotent:

[bigblu...@googlecode.com]

Status: Accepted
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 1954 by 207T...@gmail.com: Example create call not idempotent:
https://code.google.com/p/bigbluebutton/issues/detail?id=1954

What steps will reproduce the problem?

1. This create call is not idempotent and can only be issued once.

http://test-install.blindsidenetworks.com/bigbluebutton/api/create?meetingID=Meeting-24&checksum=4fbb2c49f9d0f008bb92ca10b61a9abf187afb50

What is the expected output?

The create works fine, but second call errors.
Expected SUCCESS duplicate warning on second attempt.


What do you see instead?

Call the second time gives.
<response>
<returncode>FAILED</returncode>
<messageKey>idNotUnique</messageKey>
<message>
A meeting already exists with that meeting ID. Please use a different
meeting ID.
</message>
</response>

Not a major issue, but should be documented, that no params = not idempotent

Its a feature :)




--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[bigblu...@googlecode.com]

Comment #1 on issue 1954 by 207T...@gmail.com: Example create call not
idempotent:
https://code.google.com/p/bigbluebutton/issues/detail?id=1954

Appears this issue is more "major". If "no moderator or attendee PW" is
sent, bbb-web assigns them. In a number of cases this call is not
idempotent and returns idNotUnique instead of duplicateWarning so
integration logic fails.

Im troubleshooting now, since it seems to be intermittment in a customer
implementation, and i think has to do with other params, like logoutURL and
meeting name.

The api states params need to be the same? Im just hitting the refresh in
browser on create call. so no params are changing and i get the error.

Will get some test cases asap.