From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [edbrowse-dev] Threads (fwd)
Date: Tue, 27 Aug 2019 22:46:24 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.21.1908272234510.15625@phoenix> (raw)
I confirmed that the new version has not broken anything in an intricate
website that we just got working the other day, maersk.com. You can
submit a parameter using their application and it returns information
using XHR. So it exercises several different things: form submission,
CSS issues, XHR, data attributes. Very cool, and it's all intact with
the threading version. We were also wondering about speed recently. The
XHR to retrieve container moves takes a moment, but it's not too bad. I
can't tell if it got faster because of threading.
b http://maersk.com
112782
4461
10
line after 148 has been deleted
<>
i1=MSKU0208730
<MSKU0208730>
line 1 has been updated
<TRACK>
11
<TRACK>
i1*
11833
24
2 lines after 0 have been deleted
1
?
1
lines 1 through 56 have been added
<MSKU0208730> < error_icon>
<SEARCH>
< Print>
From
Yantian
To
Felixstowe
next reply other threads:[~2019-08-28 5:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 5:46 Kevin Carhart [this message]
2019-08-28 6:25 ` Karl Dahlke
2019-08-29 3:23 ` Kevin Carhart
2019-08-29 19:46 ` Geoff McLane
2019-08-29 21:05 ` Karl Dahlke
2019-08-30 19:23 ` Geoff McLane
2019-08-30 21:26 ` Karl Dahlke
2019-08-30 22:08 ` Karl Dahlke
2019-08-31 19:05 ` Geoff McLane
2019-09-01 2:58 Kevin Carhart
2019-09-01 3:04 ` Karl Dahlke
2019-09-01 18:37 ` Geoff McLane
2019-09-02 2:48 ` Karl Dahlke
2019-09-02 18:38 ` Geoff McLane
2019-09-02 18:53 ` 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=alpine.DEB.2.21.1908272234510.15625@phoenix \
--to=kevin@carhart.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).