> At 05:05 pm 13/12/00 +1300, Nic Wise said:
> >BTW, I can't anit-recommend CGI enough - its not a good option at all.
ISAPI
> >is OK, but its a LOT of work
> >
>
> I assume you meant "anti-recommend", new buzz word Nic, but what the heck.
yeah, I was trying to double-negative it :) you get t
On Wed, 13 Dec 2000, Nic Wise wrote:
> are doing it with supports it (CGI does _not_, ISAPI may but you might have
> to hack it, ASP, JSP and Servlets definatly do). Thats nice, consistant and
> quick if you have a lot of RAM (or a small number of users), and its nice
> and easy on your database.
At 05:05 pm 13/12/00 +1300, Nic Wise said:
>BTW, I can't anit-recommend CGI enough - its not a good option at all. ISAPI
>is OK, but its a LOT of work
>
I assume you meant "anti-recommend", new buzz word Nic, but what the heck.
I've got news for you - CGI programming with Delphi is really gr
At 02:48 pm 13/12/00 +1300, Colin Fraser said:
>For example, say the user queries the DB and has a result set of say 100
>records and you only want to show 10 records at a time...
>
>Without knowing too much about this stuff, my first thought would be to have
>a hidden field or a URL parameter tha
> Without knowing too much about this stuff, my first thought would be to
have
> a hidden field or a URL parameter that holds the current record or page,
and
> have this passed back to the CGI or ISAPI app when the user clicks forward
> or back.
Pretty much the case If you hold session state
There are several ways to handle this. It depends on the number of
accesses, required response, DB server load.
1. Have each user session allocated a unique session ID and record the range
they have last accessed in a SID table. Note that anything like this
precludes the use of straight HTM
