Oh, one more implementation thing - it's conceivable for the *app*
to supply the GLX protocol encoders for extensions that the app uses
(which it has to know about, after all) and that remote servers know
about, even if the local client libraries don't. Again some mechanism
would have to be created to hook it into client GLX and dispatch.

    But really I think the only reasonable answer is that the app gets
only those extensions on indirect contexts that are supported by the GLX
in libGL.so. Even having encoder functions in the driver DSOs is going
to be darned tricky.

    Allen's point about calling conventions and stack cleanup puts the
death blow to the feasibility of generic-error or -noop routines for
unrecognized extension names, anyway.

    Jon Leech
    SGI

Reply via email to