Hi Paul, nice to hear, you are happy with tntnet.
I'm really willing to help. Lets talk about possible solutions. First of all I have this: http://gcc.gnu.org/faq.html#dso. So if we change loading to RTLD_LOCAL, we loose the chance to catch exceptions thrown from webapplications. Or at least we loose the chance to get informations about the exceptions. But I see the problem. I have some suggestions, how to solve them. Tntnet can still do a "catch (...)" and send a unknown error. We just loose the message from std::exception::what(). That's what tntnet is doing already. 1. We can change the loading mechanism by configure-flag. I don't like that, since we get different binary versions of cxxtools. 2. We can set a environvariable, which indicate, which loading mechanism to use. 3. We can introduce a additonal parameter. This is platform specific and we try to get our API platform indipendent. 4. We can add some prefix to the library name, which idicates the mode. So you can specify in tntnet.conf, which loading mechanism to use for each library separately. I like the last suggestion. If you want to load a library "myLib" with RTLD_LOCAL, you just specify e.g. "!myLib" as the library name. The loader in cxxtools sees the exclamation mark, removes it and uses RTLD_LOCAL. We do not need to change the API then. What do you think? Tommi ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
