Not really. HandlerSocket assumes that the database and the client are within a secure network, behind a firewall. So even if it sounds bad to not have any authentication, it is not as bad as it sounds. NDBAPI for MySQL Cluster is the same way.
You could add some kind of authentication or security to HandlerSocket though, but the real reason this couldn't be a GSoC project is that HandlerSocket is not actually in Drizzle yet. So the only server-side GSoC project we would be interested in is to port Memcache API (rather than HandlerSocket) to Drizzle. henrik On Fri, Mar 30, 2012 at 8:41 PM, Harsh vardhan verma <harshvardhan1...@gmail.com> wrote: > hi to all,, > there is a gsoc project to implement client side parsing with handler > sockets, which will boost up the drizzle's performance,, but the > handler socket interfaces make the port open for user to > fetch/manipulate any data, thus we need some packet filtering solution > to overcome this security compromise. The filtering solution should be > such that it takes minimal processing overhead, so to attain the > maximum advantage of handler sockets. I think its a required > functionality before the deployment of handler sockets, so can this > security measure become a GSOC project too?? > > Thanks in advance > > Harsh > > _______________________________________________ > Mailing list: https://launchpad.net/~drizzle-discuss > Post to : drizzle-discuss@lists.launchpad.net > Unsubscribe : https://launchpad.net/~drizzle-discuss > More help : https://help.launchpad.net/ListHelp -- henrik.i...@avoinelama.fi +358-40-8211286 skype: henrik.ingo irc: hingo www.openlife.cc My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : drizzle-discuss@lists.launchpad.net Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
