...I had a chat with our developer, and he says that we are basically doing exactly the same thing as specified in XEP-0166 ( abstract requirement is to establish a session between two (or more) entities which can be used to transfer an arbitrary bytestream).

The only difference is that we are using SIP as the signaling protocol instead of XMPP.

Programming should be pretty straight forward, the hard (and important) thing in order to come up with a platform- and implementation independent solution would be to write a specification for the signaling protocol with respect to desktop screen sharing everyone could agree upon. I.e where the clients could negotiate how the screen sharing would be handled, which protocol to use, .... Pretty much how video is setup. A protocol where the client and server could say "I speak RDP" or "I speak VNC".

I think that this group would be the best place to come up with that specification if we want to create support for desktop screen sharing that is not bound to a certain implementation.

 What are your thoughts?

Best regards,
Niklas

On 18/02/16 10:33, Niklas Andersson wrote:
Hi,

I didn't knew about Swift. Had a quick look at it and it is indeed interesting.

It would be great if there could be a XMPP reference implementation for how desktop screen sharing should be carried out. And if Swift could provide that baseline it would be a great starting point for other IM-clients to implement the same in order to be compatible.

We would love to see Swift implement the screen sharing features we have contributed to the FreeRDP-project. Quality is Enterprise Level and the library is written in C. Support is written mainly for X11 on Linux, but there is experimental support for Windows and Mac OS X also.

If there would be a reference implementation in Swift for example, I could approach other projects (I am connected to Pidgin) to make something compatible and cross-platform.

The only bad thing is that we must use FreeRDP head, or use their nightly builds for upcoming FreeRDP 2.0. (FYI: We have also contributed to libnice project for ICE/TURN things, many patches are already merged and available upstream but some is not yet released. They'll come in libnice 0.1.14)

Best regards,
Niklas

On 16/02/16 11:24, Kevin Smith wrote:
A polite reminder. At the moment only Swift has any ideas here, which is not good!

/K

On 12 Feb 2016, at 17:37, Kevin Smith <kevin.sm...@isode.com> wrote:

Hi folks,

Could those people who intend putting up ideas (for their own projects, don’t go suggesting things on behalf of other people, please) for GSoC students please fill in http://wiki.xmpp.org/web/Summer_of_Code_2016 in the usual format By Wednesday At The Latest. If you’re in doubt about whether you’re suitable as a mentor, please get in touch with me, but some general guidelines:

Must be willing to dedicate an hour a day (in the usual case) up to about 2 hours a day (if you’re unlucky) every work day for the duration of the summer to mentor the students.
Must be mentoring for your own software project.
Must be known and of high standing in the XSF.
Must be able to do a reasonable job of actively mentoring a student, not simply expecting them to get on with writing code unsupervised.

Any questions, please discuss.

/K
_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: jdev-unsubscr...@jabber.org
_______________________________________________
_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: jdev-unsubscr...@jabber.org
_______________________________________________

_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: jdev-unsubscr...@jabber.org
_______________________________________________

_______________________________________________
JDev mailing list
Info: http://mail.jabber.org/mailman/listinfo/jdev
Unsubscribe: jdev-unsubscr...@jabber.org
_______________________________________________

Reply via email to