[jitsi-dev] Jitsi Meet API


#1

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.

Regards,
Hristo.


#2

how about adding callbacks (node style function (err, result) { ... })? That would allow async calls in the future.

···

Am 22.10.2014 11:15, schrieb Hristo Terezov:

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.


#3

Looks great! How about passing events, such as when a conference is created? It would be great to have access to them as well.

Regards
Nicholas

···

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#4

That's very cool!

Minor suggestion: rename 'filmStrip' to 'toggleFilmStrip' (it does toggle, right?).

Regards,
Boris

···

On 22/10/14 12:15, Hristo Terezov wrote:

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.


#5

Hello,

Boris, yes it does toggle. I’ll rename it. Thanks for the report.

Nicholas, good idea. Emil proposed this too and maybe we will add it the next versions of the API.

Philipp, do you mean to add callbacks for the execution of the commands?

Thanks for the comments.

Regards,
Hristo.

···

On Oct 22, 2014, at 1:36 PM, Nicholas Wittstruck <n.wittstruck@gmail.com> wrote:

Looks great! How about passing events, such as when a conference is created? It would be great to have access to them as well.

Regards
Nicholas

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#6

Hi Hristo,

I’ve added event handling here: https://github.com/nwittstruck/jitsi-meet/tree/api-events There is an example in api_example.html.

There are a couple of issues, which is why I think that using callbacks might be indeed the better way to go: JSON.stringify doesn’t handle circular structures well, such as events or strophe messages. I’ve worked around that by replacing the circular references, but that feels more like a hack.

Regards,

Nicholas

···

On 22 Oct 2014, at 13:13, Hristo Terezov <hristo@jitsi.org> wrote:

Hello,

Boris, yes it does toggle. I’ll rename it. Thanks for the report.

Nicholas, good idea. Emil proposed this too and maybe we will add it the next versions of the API.

Philipp, do you mean to add callbacks for the execution of the commands?

Thanks for the comments.

Regards,
Hristo.

On Oct 22, 2014, at 1:36 PM, Nicholas Wittstruck <n.wittstruck@gmail.com> wrote:

Looks great! How about passing events, such as when a conference is created? It would be great to have access to them as well.

Regards
Nicholas

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#7

Hi Nicholas,

Thank you for the implementation. But I think we need to implement limited number of events like join and left a conference, not all that are currently triggered. So if we support limited number of events we can pass object using JSON.stringify that doesn’t have circular dependancies.

I’m not sure what do you mean by using callbacks. Is it the same as the approach described above?

Regards,
Hristo.

···

On Oct 22, 2014, at 5:51 PM, Nicholas Wittstruck <n.wittstruck@gmail.com> wrote:

Hi Hristo,

I’ve added event handling here: https://github.com/nwittstruck/jitsi-meet/tree/api-events There is an example in api_example.html.

There are a couple of issues, which is why I think that using callbacks might be indeed the better way to go: JSON.stringify doesn’t handle circular structures well, such as events or strophe messages. I’ve worked around that by replacing the circular references, but that feels more like a hack.

Regards,

Nicholas

On 22 Oct 2014, at 13:13, Hristo Terezov <hristo@jitsi.org> wrote:

Hello,

Boris, yes it does toggle. I’ll rename it. Thanks for the report.

Nicholas, good idea. Emil proposed this too and maybe we will add it the next versions of the API.

Philipp, do you mean to add callbacks for the execution of the commands?

Thanks for the comments.

Regards,
Hristo.

On Oct 22, 2014, at 1:36 PM, Nicholas Wittstruck <n.wittstruck@gmail.com> wrote:

Looks great! How about passing events, such as when a conference is created? It would be great to have access to them as well.

Regards
Nicholas

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#8

Hi Hristo,

definitely. For an API it makes more sense to have a stable set of events that apps can register to and in that case we don’t have the issue with circular dependencies.

Yes, I think I’m talking about the same approach as Philipp. I don’t have a fixed implementation strategy in mind, though.

Regards,

Nicholas

···

On 23 Oct 2014, at 11:07, Hristo Terezov <hristo@jitsi.org> wrote:

Hi Nicholas,

Thank you for the implementation. But I think we need to implement limited number of events like join and left a conference, not all that are currently triggered. So if we support limited number of events we can pass object using JSON.stringify that doesn’t have circular dependancies.

I’m not sure what do you mean by using callbacks. Is it the same as the approach described above?

Regards,
Hristo.

On Oct 22, 2014, at 5:51 PM, Nicholas Wittstruck <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Hi Hristo,

I’ve added event handling here: https://github.com/nwittstruck/jitsi-meet/tree/api-events There is an example in api_example.html.

There are a couple of issues, which is why I think that using callbacks might be indeed the better way to go: JSON.stringify doesn’t handle circular structures well, such as events or strophe messages. I’ve worked around that by replacing the circular references, but that feels more like a hack.

Regards,

Nicholas

On 22 Oct 2014, at 13:13, Hristo Terezov <hristo@jitsi.org <mailto:hristo@jitsi.org>> wrote:

Hello,

Boris, yes it does toggle. I’ll rename it. Thanks for the report.

Nicholas, good idea. Emil proposed this too and maybe we will add it the next versions of the API.

Philipp, do you mean to add callbacks for the execution of the commands?

Thanks for the comments.

Regards,
Hristo.

On Oct 22, 2014, at 1:36 PM, Nicholas Wittstruck <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Looks great! How about passing events, such as when a conference is created? It would be great to have access to them as well.

Regards
Nicholas

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org <mailto:hristo@jitsi.org>> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#9

Hi Hristo,

I would like to propose the following events:

conferenceCreated - conference id
recordingStarted - directory
recordingStopped - /

What do you think? I would create a pull request for these events.

Cheers,
Nicholas

···

On 23 Oct 2014, at 11:07, Hristo Terezov <hristo@jitsi.org> wrote:

Hi Nicholas,

Thank you for the implementation. But I think we need to implement limited number of events like join and left a conference, not all that are currently triggered. So if we support limited number of events we can pass object using JSON.stringify that doesn’t have circular dependancies.

I’m not sure what do you mean by using callbacks. Is it the same as the approach described above?

Regards,
Hristo.

On Oct 22, 2014, at 5:51 PM, Nicholas Wittstruck <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Hi Hristo,

I’ve added event handling here: https://github.com/nwittstruck/jitsi-meet/tree/api-events There is an example in api_example.html.

There are a couple of issues, which is why I think that using callbacks might be indeed the better way to go: JSON.stringify doesn’t handle circular structures well, such as events or strophe messages. I’ve worked around that by replacing the circular references, but that feels more like a hack.

Regards,

Nicholas

On 22 Oct 2014, at 13:13, Hristo Terezov <hristo@jitsi.org <mailto:hristo@jitsi.org>> wrote:

Hello,

Boris, yes it does toggle. I’ll rename it. Thanks for the report.

Nicholas, good idea. Emil proposed this too and maybe we will add it the next versions of the API.

Philipp, do you mean to add callbacks for the execution of the commands?

Thanks for the comments.

Regards,
Hristo.

On Oct 22, 2014, at 1:36 PM, Nicholas Wittstruck <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Looks great! How about passing events, such as when a conference is created? It would be great to have access to them as well.

Regards
Nicholas

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org <mailto:hristo@jitsi.org>> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external applications to embed Jitsi Meet conference. The changes are available in the Jitsi Meet repository (commit 667a8c149318262ded35b97ca0d429d292b3b384). You can check the documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#10

Hey Nicholas,

Hi Hristo,

I would like to propose the following events:

conferenceCreated - conference id

Hmmm ... when would you see this being triggered?

recordingStarted - directory

OK ... except maybe for the directory since that might reveal sensitive information. I think we may want to add a publicly accessible URL though and send that in deployments that allow for it.

recordingStopped - /

OK.

Emil

···

On 8.11.14, 15:50, Nicholas Wittstruck wrote:

What do you think? I would create a pull request for these events.

Cheers,
Nicholas

On 23 Oct 2014, at 11:07, Hristo Terezov <hristo@jitsi.org >> <mailto:hristo@jitsi.org>> wrote:

Hi Nicholas,

Thank you for the implementation. But I think we need to implement
limited number of events like join and left a conference, not all that
are currently triggered. So if we support limited number of events we
can pass object using JSON.stringify that doesn�t have circular
dependancies.

I�m not sure what do you mean by using callbacks. Is it the same as
the approach described above?

Regards,
Hristo.

On Oct 22, 2014, at 5:51 PM, Nicholas Wittstruck >> <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Hi Hristo,

I�ve added event handling here:
https://github.com/nwittstruck/jitsi-meet/tree/api-events There is an
example in api_example.html.

There are a couple of issues, which is why I think that using
callbacks might be indeed the better way to go: JSON.stringify
doesn�t handle circular structures well, such as events or strophe
messages. I�ve worked around that by replacing the circular
references, but that feels more like a hack.

Regards,

Nicholas

On 22 Oct 2014, at 13:13, Hristo Terezov <hristo@jitsi.org >>>> <mailto:hristo@jitsi.org>> wrote:

Hello,

Boris, yes it does toggle. I�ll rename it. Thanks for the report.

Nicholas, good idea. Emil proposed this too and maybe we will add it
the next versions of the API.

Philipp, do you mean to add callbacks for the execution of the commands?

Thanks for the comments.

Regards,
Hristo.

On Oct 22, 2014, at 1:36 PM, Nicholas Wittstruck >>>> <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Looks great! How about passing events, such as when a conference is
created? It would be great to have access to them as well.

Regards
Nicholas

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org >>>>>> <mailto:hristo@jitsi.org>> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external
applications to embed Jitsi Meet conference. The changes are
available in the Jitsi Meet repository (commit
667a8c149318262ded35b97ca0d429d292b3b384). You can check the
documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are
welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org


#11

Hi Emil,

Hey Nicholas,

Hi Hristo,

I would like to propose the following events:

conferenceCreated - conference id

Hmmm ... when would you see this being triggered?

I would see this triggered on the conferenceCreated.jingle event. This is when the focus receives the conference id, which is needed to query the rest api of the videobridge. I am aware that this event is only triggered for the focus.

recordingStarted - directory

OK ... except maybe for the directory since that might reveal sensitive information. I think we may want to add a publicly accessible URL though and send that in deployments that allow for it.

I’ve already removed the path from the response of the videobridge, which contains information about the storage setup. The directory itself does not hold a lot of sensitive information, since it is generated by jitsi and just contains a timestamp and the conference id (which is available on the client side anyway). A publicly accessible URL would be nice, though. I could add this in a second step.

Cheers
Nicholas

···

On 08 Nov 2014, at 15:56, Emil Ivov <emcho@jitsi.org> wrote:
On 8.11.14, 15:50, Nicholas Wittstruck wrote:

recordingStopped - /

OK.

Emil

What do you think? I would create a pull request for these events.

Cheers,
Nicholas

On 23 Oct 2014, at 11:07, Hristo Terezov <hristo@jitsi.org >>> <mailto:hristo@jitsi.org>> wrote:

Hi Nicholas,

Thank you for the implementation. But I think we need to implement
limited number of events like join and left a conference, not all that
are currently triggered. So if we support limited number of events we
can pass object using JSON.stringify that doesn’t have circular
dependancies.

I’m not sure what do you mean by using callbacks. Is it the same as
the approach described above?

Regards,
Hristo.

On Oct 22, 2014, at 5:51 PM, Nicholas Wittstruck >>> <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Hi Hristo,

I’ve added event handling here:
https://github.com/nwittstruck/jitsi-meet/tree/api-events There is an
example in api_example.html.

There are a couple of issues, which is why I think that using
callbacks might be indeed the better way to go: JSON.stringify
doesn’t handle circular structures well, such as events or strophe
messages. I’ve worked around that by replacing the circular
references, but that feels more like a hack.

Regards,

Nicholas

On 22 Oct 2014, at 13:13, Hristo Terezov <hristo@jitsi.org >>>>> <mailto:hristo@jitsi.org>> wrote:

Hello,

Boris, yes it does toggle. I’ll rename it. Thanks for the report.

Nicholas, good idea. Emil proposed this too and maybe we will add it
the next versions of the API.

Philipp, do you mean to add callbacks for the execution of the commands?

Thanks for the comments.

Regards,
Hristo.

On Oct 22, 2014, at 1:36 PM, Nicholas Wittstruck >>>>> <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Looks great! How about passing events, such as when a conference is
created? It would be great to have access to them as well.

Regards
Nicholas

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org >>>>>>> <mailto:hristo@jitsi.org>> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external
applications to embed Jitsi Meet conference. The changes are
available in the Jitsi Meet repository (commit
667a8c149318262ded35b97ca0d429d292b3b384). You can check the
documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are
welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev


#12

Sorry to bother you on this, should I go forward?

···

On 09 Nov 2014, at 11:15, Nicholas Wittstruck <n.wittstruck@gmail.com> wrote:

Hi Emil,

On 08 Nov 2014, at 15:56, Emil Ivov <emcho@jitsi.org> wrote:

Hey Nicholas,

On 8.11.14, 15:50, Nicholas Wittstruck wrote:

Hi Hristo,

I would like to propose the following events:

conferenceCreated - conference id

Hmmm ... when would you see this being triggered?

I would see this triggered on the conferenceCreated.jingle event. This is when the focus receives the conference id, which is needed to query the rest api of the videobridge. I am aware that this event is only triggered for the focus.

recordingStarted - directory

OK ... except maybe for the directory since that might reveal sensitive information. I think we may want to add a publicly accessible URL though and send that in deployments that allow for it.

I’ve already removed the path from the response of the videobridge, which contains information about the storage setup. The directory itself does not hold a lot of sensitive information, since it is generated by jitsi and just contains a timestamp and the conference id (which is available on the client side anyway). A publicly accessible URL would be nice, though. I could add this in a second step.

Cheers
Nicholas

recordingStopped - /

OK.

Emil

What do you think? I would create a pull request for these events.

Cheers,
Nicholas

On 23 Oct 2014, at 11:07, Hristo Terezov <hristo@jitsi.org >>>> <mailto:hristo@jitsi.org>> wrote:

Hi Nicholas,

Thank you for the implementation. But I think we need to implement
limited number of events like join and left a conference, not all that
are currently triggered. So if we support limited number of events we
can pass object using JSON.stringify that doesn’t have circular
dependancies.

I’m not sure what do you mean by using callbacks. Is it the same as
the approach described above?

Regards,
Hristo.

On Oct 22, 2014, at 5:51 PM, Nicholas Wittstruck >>>> <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Hi Hristo,

I’ve added event handling here:
https://github.com/nwittstruck/jitsi-meet/tree/api-events There is an
example in api_example.html.

There are a couple of issues, which is why I think that using
callbacks might be indeed the better way to go: JSON.stringify
doesn’t handle circular structures well, such as events or strophe
messages. I’ve worked around that by replacing the circular
references, but that feels more like a hack.

Regards,

Nicholas

On 22 Oct 2014, at 13:13, Hristo Terezov <hristo@jitsi.org >>>>>> <mailto:hristo@jitsi.org>> wrote:

Hello,

Boris, yes it does toggle. I’ll rename it. Thanks for the report.

Nicholas, good idea. Emil proposed this too and maybe we will add it
the next versions of the API.

Philipp, do you mean to add callbacks for the execution of the commands?

Thanks for the comments.

Regards,
Hristo.

On Oct 22, 2014, at 1:36 PM, Nicholas Wittstruck >>>>>> <n.wittstruck@gmail.com <mailto:n.wittstruck@gmail.com>> wrote:

Looks great! How about passing events, such as when a conference is
created? It would be great to have access to them as well.

Regards
Nicholas

On 22 Oct 2014, at 11:15, Hristo Terezov <hristo@jitsi.org >>>>>>>> <mailto:hristo@jitsi.org>> wrote:

Hello,

We implemented an API for Jitsi Meet that allows external
applications to embed Jitsi Meet conference. The changes are
available in the Jitsi Meet repository (commit
667a8c149318262ded35b97ca0d429d292b3b384). You can check the
documentation for the API here:
https://github.com/jitsi/jitsi-meet/blob/667a8c149318262ded35b97ca0d429d292b3b384/doc/api.md.

What do you think about the new API? Any comments or concerns are
welcomed.

Regards,
Hristo.
_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org <mailto:dev@jitsi.org>
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev