Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the server (videobridge) region to jingle #316

Merged
merged 4 commits into from
Sep 17, 2018

Conversation

bgrozev
Copy link
Member

@bgrozev bgrozev commented Sep 14, 2018

No description provided.

The Jingle operation set does not need to know about all of the
extensions we support (and take their configuration as parameters).
/**
* Adds a group packet extension to a {@link JingleIQ}, and a
* {@link BundlePacketExtension} to each of its contents. I.e. adds
* everything that we deem necessary to turn enable {@code bundle} in an
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extra word turn? or maybe i'm misreading this (as I'm not sure I quite follow what it's saying)

public static void addStartMutedExtension(
JingleIQ jingleIQ, boolean audioMute, boolean videoMute)
{
// FIXME Move this to a place where offer's contents are created or
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what's stopping us from doing this now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's just a stale comment, I removed it.

@@ -363,7 +397,8 @@ else if (reInvite)
}
// Existing peers SSRCs
RtpDescriptionPacketExtension rtpDescPe
= JingleUtils.getRtpDescription(cpe);
= net.java.sip.communicator.impl.protocol.jabber.jinglesdp
.JingleUtils.getRtpDescription(cpe);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i wonder if it's worth renaming this to JicofoJingleUtils to 1) avoid the long qualified naming and 2) further denote that these are jicofo-specific jingle util functions

* @throws OperationFailedException if we are unable to send a packet
* because the XMPP connection is broken.
*/
private boolean sendJingleIq(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it seems a little odd to me that we have this generic sendJingleIq function which has to then look at fields to figure out which JingleIq actually needs to be created and sent. are there not other places (which presumably trigger/call this) which already know what is happening and can create the necessary more directly?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are there not other places (which presumably trigger/call this) which already know what is happening and can create the necessary more directly?

Yes. There's only one place where this is used, and the only reason I extracted it is to avoid having the code inline (it's 50 lines of code in a method that is already over 50 lines)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok i see now. is the comment inaccurate, though? it says "creates either session-accept or transport-replace" but the code creates either session-initiate or transport-replace. and, while fixing that (unless I'm misunderstanding) could you add to the comment how it decides to make one vs the other? (it looks like it's based on the reInvite member variable or the participant having a jingle session?)

@bgrozev bgrozev merged commit 05b37ae into jitsi:master Sep 17, 2018
@bgrozev bgrozev deleted the add-server-region branch January 25, 2023 21:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants