search for: client_dict_connect

I try to create a patch to allow (proxy-)dict to use tcp connections instead of a unix domain socket. I'm replacing connection_init_client_unix with connection_init_client_ip: --- ./src/lib-dict/dict-client.c.orig +++ ./src/lib-dict/dict-client.c @@ -721,6 +721,10 @@ client_dict_init(struct dict *driver, const char *uri, struct ioloop *old_ioloop = current_ioloop; struct

...easy to overwhelm it with simultaneous clients who then get EAGAIN. If the clients do indeed immediately try again, they are successful. (An INET listening socket does not seem to have this problem, incidentally) All of this is a long-winded way of saying that I believe in lib-dict/dict-client.c:client_dict_connect() the call to net_connect_unix should be a call to net_connect_unix_with_retries() with a small timeout. It would also be useful for us if an INET socket could be used.

...ld_ioloop); > *dict_r = &dict->dict; > > to wait until the socket is ready ... > > Any idea / tips? > > Ralf It's probably cleaner to make a "proxy-tcp" driver so parsing all the funny things gets easier. Also it will require some restructing in the client_dict_connect code. Aki

Hey guys, got a question about the expire plugin. According to the wiki, the expire plugin "keeps an internal database (Berkeley DB or SQL)". I was wondering what fields in the mysql table are needed for expire to work. I assume it is setup is similar to the quota dict setup, so was just wondering what fields are required (i.e: select_field, where_field, username_field, for quota).