Screensharing with basic example

1

Hi,

we’ve modify socket.io config in erizoClient to works through https
connections. Note that you have to modify basic server including https
support (you need to create ssl key and cert previously):

var fs = require(“fs”),
var https = require(“https”);

var options = {
key: fs.readFileSync(‘key.pem’).toString(),
cert: fs.readFileSync(‘cert.pem’).toString()
};

var server = https.createServer(options, app);
server.listen(443);

I’m going to publish this thread in our developers list (
lynckia@googlegroups.com) in order to help people with the same problem!

Regards,2013/6/11 Brendan Wreford brendan@wreford.id.au

Lynckia team,

I was testing your basic example, and modifying the code to support screen
sharing (Screen sharing with Licode).

I had issues with this working. SocketIO communicates over HTTP, and I
believe this stops Chrome letting me share my screen as https is required.

Any thoughts?

Brendan.

–

Álvaro

2

Hi,

the cert key is used to access your web server. The connection to erizo
controller (using the URL in the token) is made using websockets so I think
that is not a problem.

Regards,
Álvaro2013/6/12 Wubin vvubin@gmail.com

I remember the nuve token contains a server IP address instead of a domain
name, so the browser will still complain that the cert key is not valid.
Please correct me if I am wrong.

-w

On Wednesday, June 12, 2013 5:49:25 AM UTC-4, Álvaro Alonso wrote:

Hi,

we’ve modify socket.io config in erizoClient to works through https
connections. Note that you have to modify basic server including https
support (you need to create ssl key and cert previously):

var fs = require(“fs”),
var https = require(“https”);

var options = {
key: fs.readFileSync(‘key.pem’).**toString(),
cert: fs.readFileSync(‘cert.pem’).**toString()
};

var server = https.createServer(options, app);
server.listen(443);

I’m going to publish this thread in our developers list (
lyn...@googlegroups.com) in order to help people with the same problem!

Regards,

2013/6/11 Brendan Wreford bre...@wreford.id.au

Lynckia team,

I was testing your basic example, and modifying the code to support
screen sharing (http://lynckia.com//licode/**screen-sharing.htmlhttp://lynckia.com//licode/screen-sharing.html
).

I had issues with this working. SocketIO communicates over HTTP, and I
believe this stops Chrome letting me share my screen as https is required.

Any thoughts?

Brendan.

–

Álvaro

–
You received this message because you are subscribed to the Google Groups
“lynckia” group.
To unsubscribe from this group and stop receiving emails from it, send an
email to lynckia+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

–

Álvaro

3

I remember the nuve token contains a server IP address instead of a domain
name, so the browser will still complain that the cert key is not valid.
Please correct me if I am wrong.

-wOn Wednesday, June 12, 2013 5:49:25 AM UTC-4, Álvaro Alonso wrote:

Hi,

we’ve modify socket.io config in erizoClient to works through https
connections. Note that you have to modify basic server including https
support (you need to create ssl key and cert previously):

var fs = require(“fs”),
var https = require(“https”);

var options = {
key: fs.readFileSync(‘key.pem’).toString(),
cert: fs.readFileSync(‘cert.pem’).toString()
};

var server = https.createServer(options, app);
server.listen(443);

I’m going to publish this thread in our developers list (
lyn...@googlegroups.com <javascript:>) in order to help people with the
same problem!

Regards,

2013/6/11 Brendan Wreford <bre…@wreford.id.au <javascript:>>

Lynckia team,

I was testing your basic example, and modifying the code to support
screen sharing (Screen sharing with Licode).

I had issues with this working. SocketIO communicates over HTTP, and I
believe this stops Chrome letting me share my screen as https is required.

Any thoughts?

Brendan.

–

Álvaro