Date: Sun, 28 Oct 2001 10:04:59 +0100 From: Alexander Langer <alex@big.endian.de> To: Josef Karthauser <joe@tao.org.uk> Cc: The Anarcat <anarcat@anarcat.dyndns.org>, "Simon L. Nielsen" <simon@nitro.dk>, Eric Melville <eric@FreeBSD.org>, binup@FreeBSD.org, libh@FreeBSD.org Subject: Re: current project steps Message-ID: <20011028100459.A40262@fump.kawo2.rwth-aachen.de> In-Reply-To: <20011027210157.D1534@tao.org.uk>; from joe@tao.org.uk on Sat, Oct 27, 2001 at 09:01:57PM %2B0100 References: <20011020202153.A76835@FreeBSD.org> <20011026135930.03D1637B406@hub.freebsd.org> <20011026165952.D11804@shall.anarcat.dyndns.org> <20011026221254.A36515@tao.org.uk> <20011026172027.F11804@shall.anarcat.dyndns.org> <20011026223033.A44573@tao.org.uk> <20011027131726.A68253@shall.anarcat.dyndns.org> <20011027210157.D1534@tao.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Josef Karthauser (joe@tao.org.uk): Hi! > It sounds to me that libh has its fingers in too many pies. It's not a > clean API; What is your definition of a clean API? > and should be split into several, or rely on others. Each library can be interfaced on its own. - file access (including FTP/HTTP fetch, MD5 and ZIP interface) - database stuff - UI layer - package library - disk (interface to libdisk etc) there are some dependencies, though: e.g. the package library needs the database lib, for obvious reasons. Btw: The abstraction of the place to store the package db information (you mentioned, e.g. Oracle instead of a local directory) should be trivial, since everything is handled via calls to functions of the database lib. Even more, you are using a Database object (C++), so it's very easy to just write a SQL interfacing Database object. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-binup" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011028100459.A40262>