XErrorDB in a modular world

[Enrico Weigelt]

* Soeren Sandmann <sandmann at redhat.com> wrote:

<snip>

> I do agree though that we should fix this for 7.1. Another possibility 
> than having extensions
> ship their own files might be to add a new public call to Xlb:
> 
>    XRegisterExtensionCodes (const TableOfCodes *codes)

-1 

I dont really see the benefit of adding such extra complexity and 
moving (normally platform independent) resources into binaries.

It should be enough to have one errordb for each extension. 

This would also allow load-on-demand, compression and easy user side
modifications and a better separation between code and resources
in the good old style of unix, which is not the case if evrything's 
hardcoded.

<snip>
> that extensions would call at initialization time.  The table of codes 
> could be required to exist at all times so that it would be shared between 
> all applications and never paged into memory unless it was needed.

Aehn, you want to put it into shmem ?

<snip>
> Another long term possibility would be to add the ability to have the 
> server report the messages back, although for compatibility reasons an 
> XErrorDB file would still be needed.

The server should deliver (human readable) text messages ? 
If we really implement locales - which/whose locale should it use ?


cu
-- 
---------------------------------------------------------------------
 Enrico Weigelt    ==   metux IT service
  phone:     +49 36207 519931         www:       http://www.metux.de/
  fax:       +49 36207 519932         email:     contact at metux.de
---------------------------------------------------------------------
  Realtime Forex/Stock Exchange trading powered by postgresSQL :))
                                            http://www.fxignal.net/
---------------------------------------------------------------------