xwinclip re selection polling

[Chris Twiner]

Harold,

>Excellent detective work. It looks like longjmp setjmp is the way to go.
I will give it a try someday, unless you want to do it first.

Thanks, I'll give it a bash.  Best place is right at the beginning I think, 
all the resources will be useless anyway, as they are tied to the old 
display connection.  I've not used setjmp and longjmp before (c++ guy, love 
those exceptions) so it will be a good thing anyway for me to do them (at 
least for me:-).

>The reason that catching a server reset is so important is that we
should not be killed when the server resets and we should try to connect
to the server again if it resets. Part of this makes it easy to stay
connected when a user is using XDMCP to connect to a remote machine.
Also, we can never integrate clipboard support into XWin.exe until we
can be assured that the server will not be killed when it resets.

That's what I thought the reason was, I'm still not sure that integrating 
makes that much sense, the jmp solution would seem to solve that but the 
problem with it is it rewinds the stack right back to the setjmp, that means 
that whatever else that process has been doing it's screwed.  Hence it would 
have to be forked or spawned anyway.

I'll get it restarting anyway, shouldn't take too long.

Laters,

Chris




_________________________________________________________________
Join the worldÂ’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com