Hi Evan, On Fri, Nov 20, 2009 at 08:49:07AM -0500, Evan Jones wrote: > The only extra complexity is that libdrizzle leaves the read event > enabled when the connection is "idle." This means that if the > connection breaks, I get a callback. How should I handle this > "spurious" callback? Should I just assume this is a "connection > closed" callback? Should I call some libdrizzle function? I suppose > drizzle_con_ping would work ...
Are you using libdrizzle for the client or server interface? If you have no outstanding events (waiting for a read/write), you can just remove the event entirely from libevent. If you do get an unexpected read event (whether thats an error or not), you may just want to close/free the connection with an unexpected read event. This depends on your application context really on what the correct thing to do is. -Eric _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
