There are two optimizations that we could make
bbb-web currently scans all recordings (on disk) for any matches. For site that have 1000's of recordings, this introduces a noticeable delay. We could explore using a database to keep track of recordings. This way, the queries would be quick to generate.
Add paging to the results so that if there are 500 matched recordings, for example, the client could get the first 100 (most recent), and make subsequent requests for the next 100 and so on.
highly needed
The exception raised when doing multiple calls for this API is the following
java.io.IOException: Too many open files
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)
at org.apache.tomcat.util.net.NioEndpoint$Acceptor.run(NioEndpoint.java:482)
at java.lang.Thread.run(Thread.java:748)
We definitely need some improvements here.
I wish we could give this issue a higher priority as it afects all integrations and external applications including Greenlight.
I would actually add that this can be split in two issues. One for the way the recordings are processed and a second one for the pagination.
Most helpful comment
I wish we could give this issue a higher priority as it afects all integrations and external applications including Greenlight.
I would actually add that this can be split in two issues. One for the way the recordings are processed and a second one for the pagination.