From: Tim R. <om...@ho...> - 2004-03-24 03:57:06
|
> > >Also for the record, I understand that you do not use the "FT API" for >key management, and I am not averse to providing a file selector for the >use of prpls and other plugins. > >Ethan > > > Letting the Prpl completely handle its own sockets makes sense, but I'm not sure what the rational is for letting it handle writing to and/or reading from the local file directly. Why does it need it need to do that? The API I suggested (but didn't implement) was supposed to allow the prpl to handle the socket stuff itself, but make the core handle reading to/writing from the local file. More importantly, is it better API design to let the prpl access the local file directly, or to force it to use an abstraction? --Tim Ringenbach |