http://brainstorm.ubuntu.com/item/11685/
The benefits?
- Any IM chat client which supports Jabber+jingle+jingle via transports(may not be needed), can support AV over ANY chat protocol without extra code (even new ones that don't exist at the time of programming).
- Much less code. Currently, we have to add code to EVERY client, for every different IM protocol included. With this idea, clients would only need to support the jingle JEP over Transports. This means they can spend more time working on adding features!
- Users logging into only one jabber account, will automatically be able to access all their other IM accounts on other networks.
- Obsoletes multi-IM protocol clients. Since Jabber clients could support AV over any protocol, we don't need to code for them specifically client side. Thats all handled server-side/transport server-side
- Jabber is a totally open protocol, which anyone can set up a server for. People automatically get an account with jabber, whilst maintaining support for other protocols.

CONS
- Greater CPU load on server. However, maybe not a problem, as in some cases, may simply cost a bit more to translate the AV stream, and that could be done by separate transport servers from the server. And we know CPU's with hundreds of cores will be here within 2 years anyway, so servers will be ready in time.

[112 votes] Solution #1: Auto-generated solution of idea #11685


]]> en-us Thu, 31 Jul 2008 12:16:18 +0000 Mon, 13 Oct 2008 09:37:08 +0000 QAPoll module http://brainstorm.ubuntu.com/idea/11685/ http://brainstorm.ubuntu.com/idea/164/
]]> Thu, 31 Jul 2008 21:33:28 +0000
Read the idea properly bgfeldm. This isn't about adding webcam support for all protocols.

The problem with pidgin, is that AV support needs adding for ALL protocols. By adding a new JEP to jabber, they could only support 1 protocol, which would add support for all.

And its program agnostic. Can apply to any jabber compatible client. ]]> Thu, 31 Jul 2008 22:49:23 +0000
MSN contact initiates webcam session:
1. MSN contact initiates the webcam session
2. MSN transport sees the MSN contact wants to do webcamming
3. MSN transport gives the client of the MSN contact a fake IP for P2P (this is the IP of another server that handles video)
4. MSN transport notifies the video server
5. MSN transports converts the webcam initiation request to Jingle format and sends it to the XMPP contact. The IP is replaced by the IP of the video server.

XMPP user initiates webcam session with MSN contact:
1. XMPP contact uses Jingle to initiate the webcam session
2. MSN transport gives the XMPP user the IP of the video server to send the video
3. MSN transport sends webcam request to MSN contact and includes the IP of the video server

Image:

MSN ClientMSN TransportXMPP Client
\ | /
\---Video Server---/
| |
(proprietary protocol) (Jingle)]]> Fri, 01 Aug 2008 09:10:07 +0000 skype stopped working since 8.04 due conflicts with pulse.]]> Fri, 01 Aug 2008 10:10:13 +0000 http://brainstorm.ubuntu.com/idea/6958/]]> Fri, 01 Aug 2008 11:28:06 +0000
The only extra code needed is probably just adding other im protocol AV (such as MSN)->jingle AV converters to the servers, for free support to every client.

I actually think someone should consider posting this to the official jabber/XMPP mailing lists, to see if it may be considered for the official server daemons.

]]> Sun, 03 Aug 2008 05:06:32 +0000 ]]> Wed, 10 Sep 2008 12:18:36 +0000
But this idea would benefit windows and OSX too. Because its the first time that any client could implement 1 AV protocol and automatically receive support for any.]]> Tue, 23 Sep 2008 06:48:34 +0000 Tue, 23 Sep 2008 11:05:37 +0000 Mon, 13 Oct 2008 09:37:08 +0000