To view parent comment, click here.
To read all comments associated with this story, please click here.
Every word in my post was a direct response to inaccuracies in the parent post.
Your post said: "What windows does is keeping a copy of all the video resources in system ram (then is kind of needed anyway if you need to page video ram in and out for stuff like opengl/direct3D)."
I corrected this. You also said that Windows has no client/server model, so I corrected that as well.
I mentioned off-screen windows because those are a special case on Windows, and that is the only case where they cannot be immediately recreated if the DWM client disconnects (or the server component is restarted).
I'm not an expert on X, just Windows. But it seems to me that the biggest problem for the X model is that there's too much application / window state that exists in the server process and if it goes down, there's no way to preserve that state (without explicit app participation). Window buffers / bitmaps are of no consequence and should be able to be recreated just like they are on Windows. That's why I'm confused that you brought them up.






Member since:
2006-02-25
Pheraps you should stick to reading the parent posts before answering something unrelated. I wrote about actual bitmap objects stored in video ram, not offscreen window buffers... you know those referenced with an HDC handle. In the X11 model, those are stored in the server and lost after the connection is broken.
Edited 2009-08-17 00:12 UTC