Re: Session storage vs. frequent DB calls

From: Rune (year)
Date: 07/30/04 

Date: Fri, 30 Jul 2004 16:22:18 +0200

CJM wrote:
> My answer would be that it doesnt matter.
>
> The overhead for multiple DB calls is negligible, especially when
> connection pooling is utilised. The overhead for storing so little
> information in a Session variable is negligible, unless you have an
> VERY large number of concurrent users.

Some of out previous surveys (using multiple DB calls) slowed down the
server a lot when many users were connected at the same time, so it seems to
matter.

> You could avoid both if you really wanted to: pass the concatenated
> answers to the next page (encrypted, of course) in a querystring.

The querystring can only hold 1024 characters in total, which in this case
is not enough.

> Store the concatenated answers in a hidden form field, and POST to
> each page...

This would mean transfering the same data back and forth between server and
client again and again. This seems very ineffecient.

> I'm sure there are many other weird & wonderful ways of
> doing it, but does it really matter?

Yes, I would say so. See above.

> So I would concentrate on functionality. Do you want to abandon a
> survey if not completed or do you want to salvage what you can?

The idea is that the user can log off and return later and finish the rest
of the survey. Thus we save data from unfinished surveys.

> If
> you want to keep the data from an unfinished survey, you can use the
> DB route or you could store the answers in a cookie.

We use session cookies to be able to use sessions, but we don't want to
force the user to turn on cookies for long term storage of information.
Apparently many people use high security and privacy settings.

Rune

Relevant Pages

  • Re: AU - Husband named suspect in Rayney murder
    ... He should purely inject no matter how Charles when the multiple ... threads employ by no means the mental election. ...
    (sci.engr.lighting)
  • Re: Session storage vs. frequent DB calls
    ... The overhead for storing so little ... > Some of out previous surveys (using multiple DB calls) slowed down the ... talking about but unless you really do have LOTS of concurrent users you ... survey, in which case 1024 should be plenty. ...
    (microsoft.public.inetserver.asp.general)
  • Re: database surveys?
    ... "Chinda D via AccessMonster.com" wrote: ... and option boxs for multiple questions. ... However, if this survey is ... how to prevent a form from showing existing records- to find out how. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: database surveys?
    ... You can easily contruct an data entry survey by using combo box, ... and option boxs for multiple questions. ... how to prevent a form from showing existing records- to find out how. ...
    (microsoft.public.access.tablesdbdesign)
  • Re: how to design database to handle survey data with multiple respons
    ... Are you suggesting that "At Your Survey" doesn't allow the survey designer ... > My suggestion would allow a variety of responses other than yes/no. ... >> MS Access MVP ... There is one survey question that has multiple answers ...
    (microsoft.public.access.tablesdbdesign)
Loading