API JS: Conception

[CEA-SEPIA]

Hello,

We have some structural questions about the UCengine.

The REST API and the JS API don't act in the same way. In fact, to
join a meeting in the REST API , the method is : PUT /meeting/all/
{meeting}/roster/{uid}. There isn't any organisation component in this
call. However, in the JS API, the structure is : PUT /meeting/{org}/
all/{meeting}. I don't understand why the organisation is needed at
this level. Why is this important and what is the advantage ?

Moreover, the organisation component in the JS API concerns only the
meeting's creator or each participant ? To put it in another way, if a
member of another organisation enters the meeting, do we have to
create another object with a different organisation but the same
meeting id ?

We don't understand for now why we have to compute all the objects
uce.org().meeting() in order to keep the handlers ? For us it implies
a performance loss and a more difficult developpment without any
obvious advantage. The organisation is a static variable that can be
retrieved easily at any time without being carried all the time in the
objects.

Can you please tell us more about this structure ? From a conception
point of view, we have to know if the JS API will only have to match
the REST API or will it be more something of a framework ?

Thanks in advance.