|Subject:||Re: [lwip-users] Socket read/write and threads|
|Date:||Mon, 11 Jan 2010 15:55:00 +0200|
|User-agent:||Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168) Gecko/20091204 Thunderbird/3.0|
Is the half duplex limitation only a socket implementation issue? other than the missing locks, what else is missing? using the netconn API seems to result in the same problem.
Isn't the TCPIP thread performing operations one at a time anyway?
I'm sorry. I tried thinking about this for a while but the only way I could produce any helpful code here is if I throw myself into actually coding and testing it... my boss would not like that I imagine :)
Are you working with existing vnc server code that uses two threads, or are you writing the code yourself?
If you have existing code, maybe you should try serializing the send and receive operations with a separate thread using select as I've suggested earlier.
If you are writing your own code, could you clarify why a single thread (not the main) using select and doing all Rx and Tx would not work?
On 11/01/10 11:33 AM, Nicolas Pinault wrote:
-- Yoav Nissim Software Engineer, Software Tools Division Jungo Software Technologies Email: address@hidden Web: http://www.jungo.com Phone: +972-74-7212138 Fax: +972-74-7212122 Mobile: +972-54-2271315
|[Prev in Thread]||Current Thread||[Next in Thread]|