How are multiple recordings sorted in getRecordings() API result?

[daqing]

Hi, 

I'd like to know how multiple recordings are sorted in the getRecordings() API call.

We noticed that sometimes the recordings are sorted in ASC order, sometimes in DESC order.

Yours,

Devin Zhang

[Fred Dixon]

Hi Devin,

As you've found, there is no defined sort order for the getRecordings() call.  

To get a sorted list, you could, of course, parse the contents and create as sorted list in the code that processes the result from getRecrodings().

Regards,... Fred

-- 
BigBlueButton Developer

http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

BigBlueButton on twitter: @bigbluebutton

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.
Visit this group at http://groups.google.com/group/bigbluebutton-dev?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[daqing]

well, we can do that.

But isn't it reasonable for the API to return a sorted list of recordings, either in ASC or DESC order? 

The order is important when a meeting has multiple recordings.

In our case, our training courses may be recorded twice(due to various reasons),  and we just want to show the *latest* recording to our students. 

what do you think?

[Fred Dixon]

Hi David,

> and we just want to show the *latest* recording to our students. 

We could sort the results, but how should we sort them?  Should getRecordings() sort by name, date, length, number of recordings, etc.?  Whatever we choose would not work for some.  Should we then expand the API to pass additional sort parameter, such as field and ASC and DES order?  What if some want to sort by date, then by name?  Should we further expand the API to pass a comparison function?

For logic such as the sorted order to display results to the user, this is really client-side logic that is unique to each 3rd part application that uses the API. 

In designing the BigBlueButton API, we strive to provide the simplest API possible.   And simple is good for stability, testing, and maintainability of the project.

Regards,... Fred

-- 
BigBlueButton Developer

http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

BigBlueButton on twitter: @bigbluebutton

[daqing]

can we consider `startTime` as a *natural* order, so the result won't be random?

then if 3rd parties need to implement additional sorting, they can do that based on the natural order.

[Fred Dixon]

Hi,

Opened and enhancement request.  See

  https://code.google.com/p/bigbluebutton/issues/detail?id=1492

To understand how we choose issues for each release, see

   https://code.google.com/p/bigbluebutton/wiki/FAQ#When_will_feature_X_be_implemented

Regards,... Fred

-- 
BigBlueButton Developer

http://bigbluebutton.org/
http://code.google.com/p/bigbluebutton

BigBlueButton on twitter: @bigbluebutton