In a recent project, we came across a problem using the FreeTDS (MS SQL /\nSybase DB API) libraries on a Linux box.\n\nTo cut a long story short, we ending up exposing the functions we needed\nfrom a Win32 machine, via XMLRPC, in Python, so that we could run ad-hoc\nqueries on the SQL Server which was running on that same machine.\n\nSide point: The timeliness at which I was able to achieve this impressed the\nboss. Python code is now springing up everywhere :-)\n\nI am now considering implementing persistent connections, authentication,\nand perhaps even "stored procedures" in this tiny XMLRPC Server. This would\nprovide a consistent database interface to all our applications (written in\nvarious languages) and allow us to consider things like load balancing and\nquery caching. It would also make a move from the proprietary SQL Server to\na Free RDBMS much easier (portable stored procedures, same API etc).\n\nThe problem is, I have a tiny little nag in my mind about the use of XMLRPC\n(and therefore HTTP) to implement this.\n\nHas anyone done this sort of thing before? \n\nAre there any problems with this strategy that I have not considered?\n\nShould I be considering the standard python XMLRPC / HTTP / SocketServer\nmodules for mission critical production systems?\n\nRegards,\n\nSimon Wittber.