MonetDB: default - add support for unix sockets
g.j.molenaar at uva.nl
Fri Sep 6 11:45:47 CEST 2013
On 06/09/13 11:14, Fabian Groffen wrote:
> On 06-09-2013 09:42:10 +0200, Gijs Molenaar wrote:
>> Hi Stefan, others,
>> * Is the path to the socket always /tmp.s.merovingian.<port> and
>> /tmp.s.monetdb.<port> ?
> yes, unless configured differently
>> * If not, is it okay if I just make these the defaults?
> the "/tmp/" part can be made configurable/default
ok, I did that.
>> * The SQL MAPI over the monetdb socket seems to work fine, but the
>> control MAPI seems to be quite slow and for some commands (kill)
>> is hanging or maybe not correctly implemented. The control MAPI
>> protocol over a socket is a bit weird, it differs quite a lot
>> from the other implementations. Maybe you guys have an idea what
>> is going on? i've been looking at the C code and found some hints,
>> (like you need to send a 0 at the beginning of communicating over
>> a socket, but not in the case of control), but i'm a bit stuck now.
> control and mapi are different things, socket mode doesn't use blocks,
> and doesn't login iirc
> I think the Java code has comments/explanation.
Yes, i used that as a base. But java doesn't do unix sockets, so it
didn't implement that part. And the protocol is bit different for unix
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 263 bytes
Desc: OpenPGP digital signature
More information about the developers-list