From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Setters and Post Scan
Date: Tue, 11 Mar 2014 11:26:57 -0400 [thread overview]
Message-ID: <20140211112657.eklhad@comcast.net> (raw)
> 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?
In theory it could be bad, in a contrived webpage that I wrote myself,
perhaps growing as n^2 for the number of html tags,
but in practice I don't think it will be an issue.
next reply other threads:[~2014-03-11 15:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 15:26 Karl Dahlke [this message]
2014-03-11 20:33 ` Adam Thompson
-- strict thread matches above, loose matches on Subject: below --
2014-03-11 20:59 Karl Dahlke
2014-03-12 9:45 ` Adam Thompson
2014-03-10 12:27 Karl Dahlke
2014-03-11 13:47 ` Chris Brannon
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=20140211112657.eklhad@comcast.net \
--to=eklhad@comcast.net \
--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).