Single page architecture (for program page)
John Hughes writes: Actually, the bigger problem I’ve had with it, especially later today, is that when I lose network connectivity then the page turns blank. I think this is because every action turns into an http request and page reload, rather than being handled locally in Javascript. This is visible also in somewhat slow response times if the network connection is not very fast (as it so often is not at ACM conferences!). I wonder whether you could code-generate (more of) the functionality as a single Javascript web app, so that most interactions are handled locally in the browser rather than via communication with the server? For example, there’s no reason why filtering the programme differently should involve a server communication.
Submitted by Eelco Visser on 21 January 2016 at 20:39
Issue Log
Upcoming release will have faceted filtering performed client-side. All filtering will be done client-side without any requests.
Only the starring of events and viewing event details (popover modals) will change the page using communication with the server. No reloads of the program page anymore.
Log in to post comments