The software needs a way to track who was responding to which questions. That’s because many of the questions relate to one another. It does that without requiring logins by using the ongoing http session. If you leave the survey idle then the session will time out. You can suspend a survey session by creating a login which it will then use for your answers.
The cookies thing is because it’s not a single server but loadbalanced between multiple webservers (multiactive HA architecture). This survey isn’t necessarily the only thing these servers will ever be running.
(I didn’t write the software but I am providing the physical hosting it’s running on.)
The software needs a way to track who was responding to which questions. That’s because many of the questions relate to one another. It does that without requiring logins by using the ongoing http session. If you leave the survey idle then the session will time out. You can suspend a survey session by creating a login which it will then use for your answers.
The cookies thing is because it’s not a single server but loadbalanced between multiple webservers (multiactive HA architecture). This survey isn’t necessarily the only thing these servers will ever be running.
(I didn’t write the software but I am providing the physical hosting it’s running on.)