Desktop Developers' Conference day-2

GLX

• Hardware Accelerated indirect rendaering is unsuppoerted. - want to load "client-side" DRI drivers in the server - interface between libglx and libGLcore(in server) is very differnet from interface between libGL and DRI driver(in client)
• new generation XML configuration and code-generation.

• Labor not cleanly divided between libglx and libGLcore - creation of GL visuals and drivers's internal representation mixed togher - reflects the pre-pbuffer nature of the code
  - entire process is very convoluted.

• Generate server side glx protocol code - solution: use same XML to generate the server side protocol code/ can generate up to 26000 of 30000 lines of server side protcol code. addtion: server side optimization.

• dispach table to call GL funtions. - it reduce size and load time. same as client-side.

• impacted server side code. non-unix libGLcore implementations.
  eache change to interface will break non-unix libGLcore implementation. darwin / cygwin ports must use dispatch table and new API.

• IHV support. ML, keep aware of future API changes.- old interface is removed in X.org 7.0.