A> The current method will tend to get the pages requested offline first, A> but won't do anything to guarantee this.
OK, let's discuss the order requests made offline are later fetched when online. I notice it seems it is a first in - last out order -- the requests you made longest ago will take longest to be fetched. This seems the correct strategy for requests made online: give me what I am clicking on now. But for requests made when offline: think about mail queues, or waiting at traffic lights: I've waited in line the longest, when will I get to go? I bet the exim designer wouldn't choose LIFO. But that is an all offline case, so to speak. Sure, if one can finish fetching all in one connection, who will notice the difference. All pages got fetched. But with short online sessions, we may never get to fetch those older requests, as new requests pile on top of their heads, offline or on. Hmmm, and I seem to recall /var/cache/wwwoffle/outgoing is fetched in ls -U order. Perhaps efficient, but bad: throw ordering to the winds of chance. Proposal: new variable: wwwoffle-fetch-offline-order: Default "U" (random). ls(1) switches used in ordering fetching of request made offline. Use "t" to fetch newest requests first, "tr" to fetch oldest requests first. Hmmm. Or perhaps I can do a hack to reorder the outgoing directory just before going online: mkdir outgoing.FIFO cd outgoing ln `ls -U|tac` ../outgoing.FIFO cd .. mv outgoing outgoing.LIFO #backup mn outgoing.FIFO outgoing OK, I'll see how that works. "However note, personal hacks do not benefit the masses."
