From: "Kevin Carhart" <kevin_carhart@fastmail.fm>
To: "Karl Dahlke" <eklhad@comcast.net>, edbrowse-dev@edbrowse.org
Subject: Re: possible root cause in gebcn for a recaptcha issue
Date: Wed, 20 Oct 2021 05:31:17 -0700 [thread overview]
Message-ID: <cf1f203c-d7c6-45df-a36d-db16ffe3f7ad@www.fastmail.com> (raw)
In-Reply-To: <20210920073338.eklhad@comcast.net>
Don't worry, I knew what I was signing up for in hacking a JS library written by Google.
I have read about the live arrays. So the result set is supposed to always be up to date at request time? Could this be done with a getter/setter concept? It only needs to be live Just In Time.
next prev parent reply other threads:[~2021-10-20 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 10:31 Kevin Carhart
2021-10-20 11:33 ` Karl Dahlke
2021-10-20 12:31 ` Kevin Carhart [this message]
2021-10-20 12:59 ` Karl Dahlke
2021-10-20 12:00 ` root element Karl Dahlke
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=cf1f203c-d7c6-45df-a36d-db16ffe3f7ad@www.fastmail.com \
--to=kevin_carhart@fastmail.fm \
--cc=edbrowse-dev@edbrowse.org \
--cc=eklhad@comcast.net \
/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).