Re: libproxy as external dependency

On Fri, 2008-10-24 at 11:09 +0100, Rui Tiago Cação Matos wrote:
> In this specific library case, since the API is so simple and you
> don't know you need it until you somehow check your app's settings
> it's a no-brainer really.

You could lazy-load the library when you need to access a URL, but the
point is that your app shouldn't have to know how to handle proxies or
check settings: it just asks the library to handle them.

Ross Burton                                 mail: ross burtonini com
                                          jabber: ross burtonini com

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]