On 19 October 2012 21:13, Strake <strake888_AT_gmail.com> wrote:
> On 19/10/2012, Calvin Morrison <mutantturkey_AT_gmail.com> wrote:
>> I think the largest benefit is the cache. Loading up many
>> http://google.com's would mean you'd have to reload all of the images
>> and such, whereas with one process, you wouldn't have an opportunity
>> of overlap cache.
>
> So make a local HTTP caching proxy.
>
> Alternatively, to save memory perhaps, one could use local shared
> cache files, e.g. /var/cache/surf/<hash of URL>
>
>> for unix-tooly-ness with kill, you could intercept signals and only
>> have them apply to the current window.
>
> So to kill some window, I must first switch to it, then kill it. Not
> so bothersome interactively, but quite difficult in a script.
>
> That, and KILL is uncatchable, so it would kill them all; same for STOP.
>
seems like you have a better solution than me!
very good
Received on Mon Oct 22 2012 - 01:57:15 CEST