rfb | A number of modules to support the RFB protocol

Try:

Never mind... I find out where caused the problem:

I create new objects method again when I click those button, that's why the data generated by generate button is not accessed when I use rest of the buttons.

damn boy, i have things to say :)

1. I think the main cause of your issue is interaction between loops / callbacks / cluster here is an exemple to clarify my point on loops

Replace

Ok, just found it.

Just need to transform the input$regiao into a sym. And use it with !! .

The error "Unknown protocol: RFB" is coming from the Hazelcast component, which is trying to discover other cluster instances that could be running on port 5900. In some operating systems, very often on Mac, this port is occupied by VNC (remote desktop), which responds to Payara Server in an unexpected way.

There's a solution covered for Payara Enterprise users in the Payara Knowledge Base. I have access to it and will copy the relevant parts from it here.

There are various solutions possible:

• Stop the process that occupies the port 5900 (e.g. VNC, which uses that port by default). Alternatively, you can change its port. Payara Server should then start OK.
• Configure Payara Server to use a different port for Hazelcast. If you run Payara Server according to the above solution, you can then run command: asadmin set-hazelcast-configuration --startport=5901.
• Directly edit the domain.xml in the directory glassfish/domains/domain1/config and change the port 5900 to something else. Then run Payara Server as usual.
• Or change the Hazelcast port of Payara Server at startup. First, create a text file config.txt with one line set-hazelcast-configuration --startport=5901. Then start Payara Server with asdamin start-domain --postbootcommandfile config.txt. More on this in the documentation: https://docs.payara.fish/community/docs/5.2020.4/documentation/payara-micro/asadmin/pre-and-post-boot-scripts.html

I found the solution for my question

07/05/2020 13:26:01 SSL: error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher

This means, the client and server have failed to find a common set of ciphersuites that they both support.

07/05/2020 13:26:00 Using Anonymous Diffie-Hellman mode.

07/05/2020 13:26:00 WARNING: Anonymous Diffie-Hellman uses encryption but is

07/05/2020 13:26:00 WARNING: susceptible to a Man-In-The-Middle attack.

This suggests that I am using ADH based ciphersuites in x11vnc server which are not available in the default security level in 1.1.1. This was not the case in 1.0.2.

Solution for this problem is lower the security level in use to not complain about the use of ADH.

I lowered the security level of x11vnc server from ADH:@STRENGHT to ADH:@SECLEVEL=0 & it worked.

I think WebRTC is a great solution for this, this Open Source project neko does it already. They aren't using VNC (but instead using GStreamer to capture X11), but that totally possible to change.

Since png is lossless you are wasting a lot of bandwidth on that, if possible I would encode to VPx or H264.

Are you transporting these png via the DataChannel? I would also use RTP if possible. The browser will discard late frames (and other optimizations) to make sure you get the best experience.