From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: mail.toke.dk; spf=pass (mailfrom) smtp.mailfrom=irif.fr (client-ip=2001:660:3301:8000::1:2; helo=korolev.univ-paris7.fr; envelope-from=jch@irif.fr; receiver=) Authentication-Results: mail.toke.dk; dkim=pass (2048-bit key; unprotected) header.d=irif.fr header.i=@irif.fr header.a=rsa-sha256 header.s=dkim-irif header.b=BXeHOGjO Received: from korolev.univ-paris7.fr (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]) by mail.toke.dk (Postfix) with ESMTPS id 654AB98A19B for ; Thu, 14 Jul 2022 11:58:35 +0200 (CEST) Received: from potemkin.univ-paris7.fr (potemkin.univ-paris7.fr [IPv6:2001:660:3301:8000::1:1]) by korolev.univ-paris7.fr (8.14.4/8.14.4/relay1/82085) with ESMTP id 26E9wYVQ011809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 14 Jul 2022 11:58:34 +0200 Received: from mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [81.194.30.253]) by potemkin.univ-paris7.fr (8.14.4/8.14.4/relay2/82085) with ESMTP id 26E9wYkE008370; Thu, 14 Jul 2022 11:58:34 +0200 Received: from mailhub.math.univ-paris-diderot.fr (localhost [127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTP id CA9BC3D1B; Thu, 14 Jul 2022 11:58:34 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=irif.fr; h= content-type:content-type:mime-version:user-agent:references :in-reply-to:subject:subject:from:from:message-id:date:date :received:received; s=dkim-irif; t=1657792713; x=1658656714; bh= LLMaVRDRMOmc4P5zWfBs5/NadwBmPDgG+uBVwrxbtuw=; b=BXeHOGjOnlsr5bTt fy4x1zlJG6c4GC0qWoRCYGJQAGO3z2mjwBbSsqhpRFCGd8v2sT332SU9BFJmE0uh XF2jxfdRlIfYUKyb8g6dLtl+wKSe2kAIq7iCGtNJwi0AJUyPxH8lpCjspweK5nk7 p6BU9DWecRc6zHcLp54qMpJMSHcfrtaj5pIMH2vsFOQnxQbJVDzycSDVGCbhcqpd JOwwhaOwOeUgvMDl/ndNl0chZCa28yv4BLuKjMrSMNvqyNfMpj8vyL1S6HxDHSZU sb5OmyGAlaYGXM4pHCGIxtcFYfVO3zAmxwhFLR+76XGtf6w0h0O5WPFZrFdUbhK7 tt5i7A== X-Virus-Scanned: amavisd-new at math.univ-paris-diderot.fr Received: from mailhub.math.univ-paris-diderot.fr ([127.0.0.1]) by mailhub.math.univ-paris-diderot.fr (mailhub.math.univ-paris-diderot.fr [127.0.0.1]) (amavisd-new, port 10023) with ESMTP id zSoqO8H-ytDW; Thu, 14 Jul 2022 11:58:33 +0200 (CEST) Received: from pirx.irif.fr (unknown [78.194.40.74]) (Authenticated sender: jch) by mailhub.math.univ-paris-diderot.fr (Postfix) with ESMTPSA id 3E91D3D15; Thu, 14 Jul 2022 11:58:33 +0200 (CEST) Date: Thu, 14 Jul 2022 11:58:33 +0200 Message-ID: <87ilo08186.wl-jch@irif.fr> From: Juliusz Chroboczek To: Jeroen van Veen In-Reply-To: References: <87edyp3pc5.wl-jch@irif.fr> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/27.1 Mule/6.0 MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (korolev.univ-paris7.fr [IPv6:2001:660:3301:8000::1:2]); Thu, 14 Jul 2022 11:58:34 +0200 (CEST) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (potemkin.univ-paris7.fr [194.254.61.141]); Thu, 14 Jul 2022 11:58:34 +0200 (CEST) X-Miltered: at korolev with ID 62CFE8CA.008 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-Miltered: at potemkin with ID 62CFE8CA.004 by Joe's j-chkmail (http : // j-chkmail dot ensmp dot fr)! X-j-chkmail-Enveloppe: 62CFE8CA.008 from potemkin.univ-paris7.fr/potemkin.univ-paris7.fr/null/potemkin.univ-paris7.fr/ X-j-chkmail-Enveloppe: 62CFE8CA.004 from mailhub.math.univ-paris-diderot.fr/mailhub.math.univ-paris-diderot.fr/null/mailhub.math.univ-paris-diderot.fr/ X-j-chkmail-Score: MSGID : 62CFE8CA.008 on korolev.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000 X-j-chkmail-Score: MSGID : 62CFE8CA.004 on potemkin.univ-paris7.fr : j-chkmail score : . : R=. U=. O=. B=0.000 -> S=0.000 X-j-chkmail-Status: Ham X-j-chkmail-Status: Ham Message-ID-Hash: NXGF43XNTRW26JL2J6N3ZVLN7PATWSAO X-Message-ID-Hash: NXGF43XNTRW26JL2J6N3ZVLN7PATWSAO X-MailFrom: jch@irif.fr X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: "galene@lists.galene.org" X-Mailman-Version: 3.3.5 Precedence: list Subject: [Galene] Re: Fw: Re: Versioning the Galene protocol List-Id: =?utf-8?q?Gal=C3=A8ne_videoconferencing_server_discussion_list?= Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: > Why support multiple versions of the same protocol? Wouldn't that only > complicate things at the Galene side? I don't mind personally to stick > to a version of the protocol, that was made to work with that particular > version of Galene. If the server cannot support multiple versions, then every change to the protocol breaks all non-web clients. (There's Galene-stream already, and I'd really like to see a native client for Android that can do screenshare.) > Would that be to be able to subscribe to certain kind of messages? (e.g. chat) In order to join a group, you currently do: C->S: join(groupname) S->C: joined(groupname) S->C: chathistory, chathistory, chathistory C->S: request(audio, video) There is no way to avoid receiving the chat history, and there's no way to avoid receiving chat messages. The proposed protocol is C->S: join(groupname) S->C: joined(groupname) C->S: request(audio, video, chat) S->C: chathistory, chathistory, chathistory Unless you explicitly request chat, you're not going to get the burst of chathistory messages, and you're not going to get any chat messages. > Would it be a problem to just be able to use newly added group actions > in the protocol without explicitly having to mention that it's part > of an extension? If you send a groupaction that the server doesn't know about, you'll receive an error message. It would be useful to be able to avoid exposing a group action in the UI if the server doesn't support it, and that's what the extension mechanism could be useful for. Whether this will prove necessary will depend on whether useful native clients surface. Ideally, of course, we'd have a single protocol that is used across multiple servers. Unfortunately, the only standardised videoconferencing protocols are SIP and Jingle, both of which are somewhat strange (streamed XML, giggle). -- Juliusz