On Mon, May 12, 2008 at 4:33 AM, Klaus D. Witzel <<a href="mailto:klaus.witzel@cobss.com">klaus.witzel@cobss.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Last night Igor designed the module layer and convinced me that OpenDBX can easily be made an external module (mini-driver) once it's available. Our project intends to support more than just one such mini-driver, loadable on demand. Part of this is Igor's mini-driver API which is all that needs to be adapted for making a new external DB module. And Igor insists on our plugin to manage multiple native threads and their db sessions; wink, blink ;)</blockquote>
<div><br>Wow. Smalltalk. Move fast...!<br>
<br>Plugin Name: DBPlugin...maybe this should include an OpenDBX reference since it will be based on it? OpenDBXPlugin?<br>
<br>Package Name: SqueakDB...good<br>
<br>So, if I understand...the design would work like a "meta-db" service that would dynamically load new db modules for various databases? Meaning a single service would be handling the Squeak transactions and doling them out to the correct mini-drivers?<br>
<br>And now, without knowing anything about your design, and probably sounding foolish, could your "transaction manager" be written in Squeak itself, running headless and passing requests to the appropriate drivers?<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Now, unfortunately MS$ is the platform that Rob and Frank want *now* and so OpenDBX is, for a loong, loong time, out of reach for us. This is also the reason behind our project, the *absence* of MS$ platform support.</blockquote>
<div><br>This is true!<br><br></div></div><br>