Wayland and Weston 1.0 released

The main point of the dispute IMHO is: should the protocol be designed to work well with remote display (such as XRender's glyph cache mechanism) and then use that for local display plus optimizations such as DRI2, shared memory or should the protocol be only designed to work well locally as Wayland was described initially?

Because if you add in the toolkit/application optimizations for remote display on top of a protocol designed for local use only, it is very likely that there will be interoperability issues (toolkit X with display server Y..), even if 'tookit X with display X' can be better optimized than a generic protocol.

Then again KH has said that he optimized Wayland to reduce the number of RTT, so we'll see, maybe a Wayland proxy will work well even in remote display..