Using websocket with a light thread

gg.lafon · 2014-05-03T00:27:58+00:00

Ahh, OK. So the main difference is you let the function continue to be called in each worker but only do some work if you grab the lock.I think at some point...

Using websocket with a light thread

gg.lafon

Hello agentzh,

when could you include in Openresty the patch from aviramc in order to use the same websocket in the main Lua execution code and in a light thread?

It's very useful, otherwise an error socket busy is thrown.

https://github.com/aviramc/lua-nginx-module/tree/socket-changes

Thank you

Jérôme

agentzh

Hello!

On Fri, May 2, 2014 at 9:27 AM, Jerome Lafon wrote:
> when could you include in Openresty the patch from aviramc in order to use
> the same websocket in the main Lua execution code and in a light thread?
> It's very useful, otherwise an error socket busy is thrown.
> https://github.com/aviramc/lua-nginx-module/tree/socket-changes
>

Those patches are still in my review queue. They might get merged in
the coming weeks or months. Bug fixes and optimizations usually take
priority over such new features though.

Regards,
-agentzh

kostik.hunter

Hi all!

Yes, those patch is very useful. It's still possible to live without that, but you need to do some tricks.

gg.lafon

Hello,

This patch is very useful because it prevents using two sockets for bidirectionnal communication.

Jérôme

Le lundi 5 mai 2014 08:58:48 UTC+2, Константин Буркалев a écrit :

Hi all!
Yes, those patch is very useful. It's still possible to live without that, but you need to do some tricks.

gg.lafon

Hello,

I tried to compile the latest version of Openresty with the lua-nginx-module from https://github.com/blablacio/lua-nginx-module

But I have an error running resty postgres module:

resty/postgres.lua:183: bad argument #3 to 'connect' (bad\

"ssl" option type: nil)

The line 183 in postgres.lua is: ok, err = sock:connect(host, port, { pool = pool })

Could you help me please?

Thank you

Jérôme

Le vendredi 2 mai 2014 18:27:57 UTC+2, Jerome Lafon a écrit :

Hello agentzh,

when could you include in Openresty the patch from aviramc in order to use the same websocket in the main Lua execution code and in a light thread?
It's very useful, otherwise an error socket busy is thrown.
https://github.com/aviramc/lua-nginx-module/tree/socket-changes

Thank you
Jérôme

manchev

Well, looking at the error I think the ssl parameter is mandatory and you should add it to the sock:connect line.

Take a look at the comment here for an example: https://github.com/openresty/lua-nginx-module/pull/290#commitcomment-5202406

Best,
Vladislav

On 05/09/14 18:35, Jerome Lafon wrote:

Hello,
I tried to compile the latest version of Openresty with the lua-nginx-module from https://github.com/blablacio/lua-nginx-module

But I have an error running resty postgres module:

resty/postgres.lua:183: bad argument #3 to 'connect' (bad\

"ssl" option type: nil)

The line 183 in postgres.lua is: ok, err = sock:connect(host, port, { pool = pool })

Could you help me please?

Thank you

Jérôme

Le vendredi 2 mai 2014 18:27:57 UTC+2, Jerome Lafon a écrit :

Hello agentzh,

when could you include in Openresty the patch from aviramc in order to use the same websocket in the main Lua execution code and in a light thread?

It's very useful, otherwise an error socket busy is thrown.

https://github.com/aviramc/lua-nginx-module/tree/socket-changes

Thank you

Jérôme

.

gg.lafon

Thanks a lot, it seems to work!

Le vendredi 9 mai 2014 18:56:56 UTC+2, Vladislav Manchev a écrit :

Well, looking at the error I think the ssl parameter is mandatory and you should add it to the sock:connect line.

Take a look at the comment here for an example: https://github.com/openresty/lua-nginx-module/pull/290#commitcomment-5202406

Best,
Vladislav
On 05/09/14 18:35, Jerome Lafon wrote:

Hello,
I tried to compile the latest version of Openresty with the lua-nginx-module from https://github.com/blablacio/lua-nginx-module

But I have an error running resty postgres module:

resty/postgres.lua:183: bad argument #3 to 'connect' (bad\

"ssl" option type: nil)

The line 183 in postgres.lua is: ok, err = sock:connect(host, port, { pool = pool })

Could you help me please?

Thank you

Jérôme

Le vendredi 2 mai 2014 18:27:57 UTC+2, Jerome Lafon a écrit :

Hello agentzh,

when could you include in Openresty the patch from aviramc in order to use the same websocket in the main Lua execution code and in a light thread?

It's very useful, otherwise an error socket busy is thrown.

https://github.com/aviramc/lua-nginx-module/tree/socket-changes

Thank you

Jérôme

.

aaashun

Hi, all

I've submitted a patch just now which implements duplex-cosocket. For details please see https://github.com/openresty/lua-nginx-module/pull/367

On Saturday, May 10, 2014 7:25:54 PM UTC+8, Jerome Lafon wrote:

Thanks a lot, it seems to work!

Le vendredi 9 mai 2014 18:56:56 UTC+2, Vladislav Manchev a écrit :

Well, looking at the error I think the ssl parameter is mandatory and you should add it to the sock:connect line.

Take a look at the comment here for an example: https://github.com/openresty/lua-nginx-module/pull/290#commitcomment-5202406

Best,
Vladislav
On 05/09/14 18:35, Jerome Lafon wrote:

Hello,
I tried to compile the latest version of Openresty with the lua-nginx-module from https://github.com/blablacio/lua-nginx-module

But I have an error running resty postgres module:

resty/postgres.lua:183: bad argument #3 to 'connect' (bad\

"ssl" option type: nil)

The line 183 in postgres.lua is: ok, err = sock:connect(host, port, { pool = pool })

Could you help me please?

Thank you

Jérôme

Le vendredi 2 mai 2014 18:27:57 UTC+2, Jerome Lafon a écrit :

Hello agentzh,

when could you include in Openresty the patch from aviramc in order to use the same websocket in the main Lua execution code and in a light thread?

It's very useful, otherwise an error socket busy is thrown.

https://github.com/aviramc/lua-nginx-module/tree/socket-changes

Thank you

Jérôme

.

gg.lafon

Thank you!

Jérôme

Le mardi 13 mai 2014 18:12:26 UTC+2, aaashun a écrit :

Hi, all

I've submitted a patch just now which implements duplex-cosocket. For details please see https://github.com/openresty/lua-nginx-module/pull/367

On Saturday, May 10, 2014 7:25:54 PM UTC+8, Jerome Lafon wrote:
Thanks a lot, it seems to work!

Le vendredi 9 mai 2014 18:56:56 UTC+2, Vladislav Manchev a écrit :

Well, looking at the error I think the ssl parameter is mandatory and you should add it to the sock:connect line.

Take a look at the comment here for an example: https://github.com/openresty/lua-nginx-module/pull/290#commitcomment-5202406

Best,
Vladislav
On 05/09/14 18:35, Jerome Lafon wrote:

Hello,
I tried to compile the latest version of Openresty with the lua-nginx-module from https://github.com/blablacio/lua-nginx-module

But I have an error running resty postgres module:

resty/postgres.lua:183: bad argument #3 to 'connect' (bad\

"ssl" option type: nil)

The line 183 in postgres.lua is: ok, err = sock:connect(host, port, { pool = pool })

Could you help me please?

Thank you

Jérôme

Le vendredi 2 mai 2014 18:27:57 UTC+2, Jerome Lafon a écrit :

Hello agentzh,

when could you include in Openresty the patch from aviramc in order to use the same websocket in the main Lua execution code and in a light thread?

It's very useful, otherwise an error socket busy is thrown.

https://github.com/aviramc/lua-nginx-module/tree/socket-changes

Thank you

Jérôme

.

cbyerley

I look forward to this patch. Wish I could help. Thank you everyone for all the hard work.

Cheers.

On Friday, May 2, 2014 11:27:57 AM UTC-5, Jerome Lafon wrote:

Hello agentzh,

when could you include in Openresty the patch from aviramc in order to use the same websocket in the main Lua execution code and in a light thread?
It's very useful, otherwise an error socket busy is thrown.
https://github.com/aviramc/lua-nginx-module/tree/socket-changes

Thank you
Jérôme