On Thu, Jun 30, 2011 at 12:33 AM, Andrew Hutchings <[email protected]> wrote: >>> For a client library we want as little dependencies as possible. In fact >>> I >> >> Why? >> Most apps should use pre-packaged libs, in which case this >> compile-time dependency isn't a problem. > > For a number of reasons. One I can think of straight away is it makes > packaging/distribution for OEM app writers that rely on these libraries more > difficult.
How do they package/distribute the client lib? >>> can't see why a library will need a .ini file. In my opinion the client >>> app >>> should have the .ini parser and use function/method calls to setup the >>> library. >> >> To read drizzle.conf / mysql.conf for defaults (host, port, socket, >> user, pass, database). > > Again, in my opinion the app should handle that and pass the results to the > library. Especially if you have two apps/instances of an app using the same > library that need to connect to different servers (very common). Why can't both ways be supported? -- Olaf _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
