From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Setters and Post Scan
Date: Tue, 11 Mar 2014 06:47:45 -0700 [thread overview]
Message-ID: <87zjkwx2wu.fsf@mushroom.PK5001Z> (raw)
In-Reply-To: <20140210082719.eklhad@comcast.net> (Karl Dahlke's message of "Mon, 10 Mar 2014 08:27:19 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> The fact that js could completely rearrange the page,
> makes it likely that we will move away from setters and towards
> a post scan for these things.
I think so. I don't think it would really be feasible to handle a fully
dynamic page in setters. How expensive is this going to be in terms of
runtime?
-- Chris
next prev parent reply other threads:[~2014-03-11 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 12:27 Karl Dahlke
2014-03-11 13:47 ` Chris Brannon [this message]
2014-03-11 15:26 Karl Dahlke
2014-03-11 20:33 ` Adam Thompson
2014-03-11 20:59 Karl Dahlke
2014-03-12 9:45 ` Adam Thompson
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=87zjkwx2wu.fsf@mushroom.PK5001Z \
--to=chris@the-brannons.com \
--cc=Edbrowse-dev@lists.the-brannons.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).