The fail or success of accessing same socket on 2 thread is depend on OS, which lwip ported on. If that OS support multi task/process/thread, i think it is ok. Am i right?
Regarding FramBufferUpdate command i am clear.
Thanks, Thien
On Wed, Sep 15, 2010 at 1:54 PM, Nicolas Pinault <address@hidden> wrote:
Hi Thien,
hi Nicolas,
I can access the same socket with 2 tasks in lwip, what's the
problem did you mention?
Yes, it works. Or, I shall say it seems to work. Lwip is not thread
safe. Accessing the same socket in two different threads is not
safe. Your system will bug/hang/crash sooner or later.
This means you have to modify the original code.
Anyone to know vnc server can actively send FrameBufferUpdate
command to vnc client (without receiving FrameBufferUpdate Request
command from client) to inform client that the screen of server
was changed?
The server always sends screen data when it wants/needs to. The
server may send only part of screen data that have changed.
The client can request a screen update when needed. At startup for
example.
Vnc protocol is simple. You can find the reference document here :
http://www.realvnc.com/docs/rfbproto.pdf
As a client, I recommend using ThighVnc 1.3.10 as it is simple
(http://www.tightvnc.com/download.php). Configure viewer to suit
server settings.
At the opposite, UltraVnc tries to find server settings
automatically but this does not work correctly with the code I use.
Regards,
Nicolas
thanks and best regards,
Thien
On Thu, Mar 4, 2010 at 7:09 PM, Nicolas
Pinault <address@hidden>
wrote:
Thien,
Be careful that, with lwip, it is not safe to access the
same socket
with 2 tasks (as it is done in the sample code).
Regards,
Nicolas
Le 04/03/2010 08:59, PHAM ANH THIEN a écrit :
hi Nicolas,
thanks a lot. I will check it.
kind regards,
Thien
On Thu, Mar 4, 2010 at 2:53
PM, Nicolas
Pinault <address@hidden>
wrote:
Hi,
Dear all,
Has anyone ported vnc server to FreeRTOS
& lwip stack? could you
please share it with me?