Philip Stoev wrote:
Hello,
I am currently developing a Perl module that will handle the MySQL protocol
server-side, allowing the creation of mysql-like servers that will answer
queries from external data (e.g. another database via DBI, etc.)
I would like to ask how do you think this module should be named. The person
that has previously worked on that called his code Net::MySQLd (not released
on CPAN), however I am aiming for a module that does more than read() and
write() so I thought something in the DBIx namespace would be appropriate.
After all, it would be possible to construct a replacement of
DBI::ProxyServer using this module and the mysql protocol rather than RPC.
At the same time, I wanted to avoid any run-ins with MySQL's patent
department, that is why I though DBIx::OurPerl would be appropriate and at
the same time will unfortunately be completely non-descriptive.
Thank you in advance for any suggestions.
Philip Stoev
First, let me offer kudos on this, I'd love to see it. What version
of the MySQL protocol will you be implementing ?
E.g., plugging DBIx::Chart into this would let MySQL
JDBC/ODBC clients render charts directly from SQL.
(Any volunteers to do a Pg version ? ;^).
That said, I'd vote against using a DBIx toplevel namespace as this doesn't
strictly
have a data mgmt purpose (unless the add'l functions you hint about will be
doing
that). The original Net::MySQLd is probably a good start, as there's
already a Net::MySQL to implement the client side. Or maybe Net::MySQLServer
to better disambiguate.
OTOH, there's an equivalent module for Sybase/TDS called Sybase::TdsServer,
and there's at least one MySQL toplevel module, so MySQL::ServerSide might be
reasonable as well.
Dean Arnold
Presicient Corp.
