Jon: On 31.05.2010 17:08, Sahananda (Jon) Wolfers wrote: > The more I think about this the less happy I become. Don't worry, be happy! ;)
> Rony's solution would also mean that all RDBMS interaction would have > to go through the daemon as it sits on the thread where the > connections work, and so that is not the main thread the interpreter uses. This depends on the DLL you are using. If RexxSQL is able to establish independent connections to RDBMS, each using a different thread for communication, then you should be able to create as many individual server daemons with independent connections to the RDBMS, with the restriction that all communication with a particular connection must occur on the thread that was used to establish the connection in the first place. I just do not know how RexxSQL behaves. (It could be e.g., that only one connection per process is allowed and that one must use the thread in which the connection was established for communication.) The documentation, readme should tell that, maybe Mark Hessling as the author can shed some light on this question, if the RexxSQL documentation does not help. --- Ad happiness: actually I think you could turn into a happy man quite quickly, depending on the answer you can come up with w.r.t. the RexxSQL thread-related rules. Please post them, once you can clarify those rules. Regards, ---rony ------------------------------------------------------------------------------ _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
