2006-08-02: Bob Copeland dixit: > Wait, what are we talking about here? Having lk_karma_connect > return the device type? I was asleep during the lkarmafs > discussion -- what is it needed for again? > > Right now, lk_karma_connect returns the socket file descriptor > when using the net, and that certainly can't be changed without > a fair amount of rework.
Right. I'd almost forgotten how the net version worked... > Personally, I'd like to see lk_karma_connect() return an opaque > lk_context_t* or something like that, so we can stick our > globals in it and make it thread safe. But that's a fairly big > departure from where it is right now. Agree. Then, for now I'll just amend a bit the riocp part we've been discussing, make an HG patch (will be changeset 94) and post a tarball in SF with the name libkarma-0.0.5-pre1 (looks like Franky is not hearing the list these days...). We can discuss how to make these things clean for another release. BTW, I think libkarma version numbers should already step forward one digit; i.e., libkarma-0.1.0. We do need at least one (the last) digit to name interesting or necessary versions between major releases. Otherwise, we have to give them strange names such as "libkarma-0.0.4-hg70". Best, EV. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-karma-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linux-karma-devel
