> > called from applications. An we already have it. It's a matter > > of changing whatever necessary so that it makes all the work and > > returns -1 if fail, 0 if connected through Ethernet and 1 if USB. > > > > What do you think? > > If this returns the device type then that removes the need for the > extra function that we were discussing in relation to lkarmafs. > So it all seems to work out nicely.
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. 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. -- Bob Copeland %% www.bobcopeland.com ------------------------------------------------------------------------- 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
