Re: Library defaults

[Davis Herring]

> So it's really: Make the defaults developer-friendly or source code
> friendly?  Because all calls from applications will end up looking like
>
> (with-url ("http..." :cookies t
>                      :cache t
>                      :verbose 0)
>    ...)
>
> And that's kinda sad, too.

No, they should end up looking like

(with-url ("http..." :cookies client4--cookies
                     :cache client4--cache)
  ...)

because it is not only the _fact_ of using cookies and cache but also 
the contents of those data stores that should be client-specific. 
Cookies serve as a "persona" that should be under the control of the 
client/user, and the client/user may know when a cache is stale or 
unneeded and want to clear it themselves.  (I imagine there is also a 
privacy concern if two personas are used but they share a cache that can 
be detected via logging the HEAD requests that do not produce a GET.)

In case it's not obvious, client4 would if appropriate offer a 
"don't-use-cookies/cache" customization that caused 
client4--cookies/cache to be nil.

Davis

PS - Yes, non-verbose should be the default, but that is indeed merely a 
stylistic concern.

--
This product is sold by volume, not by mass.  If it appears too dense or 
too sparse, it is because mass-energy conversion has occurred during 
shipping.