On 10/3/20 10:18 AM, Tom Browder wrote:
> What I have been doing with SSI is executing some fairly involved db programs
> to
> track and update the visitor's who use the site, but the handling delay during
> page load is getting too large. I suspect I could speed them up but haven't
> looked
Definitely SQLite will be a bottle neck in this system – not great for writing
to – both Pg or MySQL would be an almost certainly better solution for repeated
writing to.
You could get some simple gains by splitting the database up so that there is a
database per site rather than a database
IMHO, Web Sockets aren't going to get you any real benefit here. The primary
point of web sockets is to keep a bidirectional conversation open for the long
term during a visitor's session which makes it super beneficial to something
like an infinite scroll, but it sounds like your problem is a
I frames have their use – but usually to include content from another site
(e.g. google maps, you tube etc) – or to embed dynamic content that either
needs to be dynamically updated and can’t do this with AJAX or you are
struggling with CSS clashes as the iframe is a different document. Not
There are a number of things you can do:
1) Why are you doing what you are doing - i.e. why are you updating what is
displayed to the user
2) Others have suggested using AJAX, another thing you can look at here is what
and how you are retrieving the data.
You can look at using a cleanup
On Sun, Oct 4, 2020 at 04:38 Rob De Langhe
wrote:
> I simply use (or dynamically construct) a page with iframes, in which each
> iframe gets loaded by a separate CGI results;
>
Hm, I've always thought that iframes were frowned upon in modern practice.
I'll have to read up on them
Thanks, Rob.
hi Tom,
I simply use (or dynamically construct) a page with iframes, in which
each iframe gets loaded by a separate CGI results;
this is the async way. You can trigger the loading of certain iframes
when user clicks on some button in the main part of the page, then a
Javascript function
