Hi all, The recent issues with nbd-server 3.10 (and something else that I still need to work on -- sorry Tuomas) have convinced me that perhaps the braindeadedness of nbd-server is too bad to continue as is, and that it is time to start over. I've always tried to avoid a reimplementation, because I wasn't convinced that it would improve the situation, but I can't ignore the existing issues anymore.
Also, the lack of other people helping out with the source base have held me back in that area; but perhaps this lack of interest is mainly due to the fact that the code is so badly readable...? There have been a few (abortive) attempts at modifying the internal architecture of nbd-server (the most recent of which is the io_transaction branch), but I realize now that these can't really do what is needed to get things back into a manageable state. So, I think it's (well past) time to throw out the old code base and start anew. Before I plunge myself in there, though, I'd like to know if anyone is interested in helping out with that. I do think I can get it done myself if needed, but it's always useful to at least have someone with a second opinion, so that I can be corrected when I'm about to make a mistake. If anything, the fact that the current codebase is... not so good, is probably because of the lack of that, currently. Any takers? -- It is easy to love a country that is famous for chocolate and beer -- Barack Obama, speaking in Brussels, Belgium, 2014-03-26 ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Nbd-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nbd-general
