From: lsworkemail112 at gmail.com (Luke SanAntonio)
Subject: [PATCH] Added code to output the age as seconds instead of "0 min."
Date: Sat, 29 Sep 2012 15:16:55 -0400 [thread overview]
Message-ID: <CA+g5j+20iZeFWM=9etzvoiV88Rmn66gcPgB5gjsqpwMu6tvuGw@mail.gmail.com> (raw)
In-Reply-To: <CA+g5j+2iHEjNRS+z8UVc7oRo+FZxQTZ4ctCT7M=vUeq86584xQ@mail.gmail.com>
"reflect the actual data up-to-date" should be: "reflect the actual,
up-to-date data..."
Sorry about that...
On Sat, Sep 29, 2012 at 3:14 PM, Luke SanAntonio
<lsworkemail112 at gmail.com> wrote:
> Okay, I understand now.
> I guess my take on the matter is a user who selects caching already has accepted
> that the data generated might not correctly reflect the actual data
> up-to-date... these users
> know it going in, so I don't think it's a huge concern...
>
> Sorry about my previous misunderstanding...
> - Luke
>
> On Sat, Sep 29, 2012 at 2:51 PM, Jason A. Donenfeld <Jason at zx2c4.com> wrote:
>> On Sat, Sep 29, 2012 at 8:43 PM, Luke SanAntonio
>> <lsworkemail112 at gmail.com> wrote:
>>> Hi Jason,
>>>
>>> First of all, good call with the cache, it hadn't even crossed my mind...
>>> Second I think the cache isn't something we need to worry about...
>>> mostly because
>>> cgit is very lightweight, and I think for now, we don't have to be too
>>> worried about
>>> performance, correct me if I'm wrong though... Also it seems to me
>>> that with or without the cache,
>>> every cgit page I've ever come across seems to load in much less time
>>> than a second...
>>
>>
>> Hey, sorry, just to be clear -- my concern isn't about performance,
>> but about this:
>>
>> If you set the cgit cache to 1 minute, and the granularity of
>> timestamps is only 1 minute, then for the most part, the pages, though
>> cached, will see up to date.
>>
>> However if you set the cgit cache to 1 minute, and the granularity of
>> the timestamps is 1 second, then for the most part, the pages will
>> seem out of date.
>>
>> But this is just how caching is, so I'm not sure it's such a big
>> concern. Just throwing it out there, in case anyone had some elegant
>> solution or attitude about it.
next prev parent reply other threads:[~2012-09-29 19:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 1:39 Maintaining My Own Cgit Tree Jason
2012-09-27 4:22 ` william.bell
2012-09-27 9:00 ` Tobias.Bieniek
2012-09-27 15:53 ` webmaster
2012-09-29 0:30 ` [PATCH] Added code to output the age as seconds instead of "0 min." lsworkemail112
2012-09-29 5:20 ` Jason
2012-09-29 18:43 ` lsworkemail112
2012-09-29 18:51 ` Jason
2012-09-29 19:14 ` lsworkemail112
2012-09-29 19:15 ` Jason
2012-09-29 19:17 ` lsworkemail112
2012-09-29 19:16 ` lsworkemail112 [this message]
2012-09-30 5:51 ` mailings
2012-09-30 17:28 ` lsworkemail112
2012-09-30 17:29 ` Jason
2012-09-30 17:40 ` mailings
2012-09-30 21:06 ` lsworkemail112
2012-09-30 21:33 ` Jason
2012-10-01 6:12 ` mailings
2012-10-02 1:46 ` lsworkemail112
2012-10-02 2:04 ` Jason
2012-10-02 2:08 ` lsworkemail112
2012-10-01 13:56 ` webmaster
2012-10-08 16:48 ` [PATCH 1/2] add git config parsing during scan-path jamie.couture
2012-10-08 16:48 ` [PATCH 2/2] update documentation jamie.couture
2012-10-08 21:05 `
2012-10-08 21:18 `
2012-10-08 16:49 ` [PATCH] repolist pagination changes jamie.couture
2012-10-08 21:39 ` Jason
2012-10-08 17:12 ` [PATCH] add tag target to generate ctags jamie.couture
2012-10-08 21:41 ` Jason
2012-10-09 10:56 ` [PATCH] add git config parsing during scan-path jamie.couture
2012-10-09 11:33 ` Jason
2012-10-09 11:15 ` Maintaining My Own Cgit Tree mailings
2012-10-09 11:18 ` Jason
-- strict thread matches above, loose matches on Subject: below --
2012-08-18 20:37 [PATCH] Added code to output the age as seconds instead of "0 min." lsworkemail112
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CA+g5j+20iZeFWM=9etzvoiV88Rmn66gcPgB5gjsqpwMu6tvuGw@mail.gmail.com' \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).