* [edbrowse-dev] Fun Things to do
@ 2019-08-25 19:16 Karl Dahlke
0 siblings, 0 replies; only message in thread
From: Karl Dahlke @ 2019-08-25 19:16 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
* Often you go from one page to the next to the next on a website, all calling the same js and css files.
Yes, we issue a head request then pull them out of cash, which is pretty good, but they're already in edbrowse, and these pages are very static,
so if we pulled or verified the page within the past few hours,
it's probably fine to use the same data that is already sitting in the parent page.
Would save time and also space.
If more than a few hours then ok issue the head request and confirm, but then point to the earlier data.
Implement a new mini-cache at the end of the file cache.c, apart from the disk cache, only for js and css files, and have we seen this and if yes we are holdlding the data, and ongoing script tags can use this as their script data,
* Download large files in background, and the experimental downloading of all the js and css files in background and in parallel, which all modern browsers do,
because it speeds things up especially for a new uncached website,
we do this by forking processes which is bad at many levels.
So bad that it doesn't work (for https) at all under gnutls, though it does work under openssl.
We neeed to convert all this to threads.
I'm not worried about windows any more, so we only need understand the standard unix thread manager.
Anyone feel like tackling one of these?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-08-25 19:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-25 19:16 [edbrowse-dev] Fun Things to do Karl Dahlke
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).