Sounds like a job for AJAX, but before throwing out the baby with the bath water I'd seriously consider turning up logging with timestamps on your existing CGI and seeing if SSI is a loser in its entirety or if it's one specific part of the process that is tanking your page load times that you can easily fix (you don't say much about that data store, but if you've crossed a tipping in regards to size or number of records, you may need to reconsider your data storage strategy).
Also, if you've got really old / dumb clients AJAX might not be a great answer whereas SSI is always entirely under your control. Best of luck, Scott ________________________________ From: Tom Browder <tom.brow...@gmail.com> Sent: October 3, 2020 2:08 PM To: users@httpd.apache.org <users@httpd.apache.org> Subject: [users@httpd] Re: Alternatives to SSI (server side includes)? On Sat, Oct 3, 2020 at 12:18 Tom Browder <tom.brow...@gmail.com> wrote: > I have been using server side includes since I started my websites on Apache ... > Any suggestions for SSI replacement with a more asynchronous method? Let me be more specific about the data flow I'm using with the landing (home) page of my websites: + the first SSI line executes a CGI program that extracts the CGI and SSL variables and their values. Data of interest include: requesting IP, email address in the SSL client certificate, time of page load + the second line executes a CGI program that generates a link to a page that presents the current and past statistics of the visitor based on the stats in the db updated with the first CGI program -Tom --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
