Click to See Complete Forum and Search --> : Question: client-Server - How do you get value's on the server site


nkamp
04-20-2006, 03:14 AM
Hello,

I've already put more or less the same question about this subject on the forum. But if I understand it well then the only way to get the value's on the server is with a submit? Or.... are there at least with ASP some other opportunities?

I'm new to client-server with ASP/JS and I have to maintain a application.
In the application you can search with a selection criteria for specific records. After the search you can choose the specific record and go to the detail page. The value's of this selection criteria are on this moment saved in a hiddenframe. If you come back on the search page then the selection criteria fields are filled by JS from the hiddenframe. So far so good. But then further in the code the value is retrieved by ASP with request. Like:

objParams.add "cccccc" , Request("objValueSelCriteria").
But this is the problem the objvalue is not known on the server site. So my list is not build again according to the selection criteria what I see at the client site.

Alternative:
1. Parsing the value's with POST en GET methods in the URL. Then I don't have to made changes in the rest of the code and I can retrieve the value with a Request because the value is known on the server know. Disadvantage: first you have to send the value's to next screen and when you come back you have to parse these value's back again. And if you switch between more screens you have to take every time the value's with you.
2. With cookies. Disadvantage: not every user is allowed to use cookies.
3. OR does anyone know another smart opportunity?....

Thanks in advance.

Nico

Ubik
04-20-2006, 09:32 PM
You pretty much nailed it.

The only other thing you might consider if the user is authenticated, keep the data in a temporary spot on the server and request it when that user makes a jump to another page. You could store it in a database or something, so that you do not have to parse it each time.

Then, when the user is un-authenticated (logout), then throw the data away as part of the logout process.

Terrorke
04-21-2006, 02:09 AM
Make sure you don't generate to much database traffic. It isn't so good for preformance.

I think you could also store the values in session objects

Grtz