[privoxy-devel] Threads and csp handling in chat() and listen_loop()

[<os...@ho...>]

Greetings to everyone,

	listen_loop fills a client_state structure and passes a pointer to 
it to chat(). As I see it, in a multi-threaded environment (not fork(), 
but Win32 threads, pthreads, etc.), the main loop in listen_loop doesn't 
have to wait for chat() to complete before going to the top again and 
filling up the csp with possibly different data. Couldn't this 
conceptually interfere with chat? both these threads are asynchronously 
operating on the same memory without any locks.
	I'd be grateful if someone would point out if and where I erred.

	TIA.

-- 
"Lies, lies, all is lies! Yet beyond I tell you, beauteous and eternal
stands the Truth, Macumazahn."
 - Zikali