One can do what you suggest in a Servlet, but it is not so as simple as you
suggest and, WORSE, it can take too much resources.

Do you develop Web applications?

IF not, try to imagine that:
- You have hundred users at once each doing their own thing;
- Modern sites (as modern customers demand) always allow users to make
really fancy searches over really big amounts of data that have to
be paged trough.

It is not as easy as with normal Windowz apps.


Have fun,
Paulo Gaspar

> -----Original Message-----
> From: Doug Chamberlin [mailto:dchamberlin@...]
> Sent: Friday, June 01, 2001 12:48 AM
> To: IBDI@yahoogroups.com
> Subject: Re: [IBDI] Firebird 1
>
>
> All this talk of "browsing" result sets and sending back sections of them
> suggests an application server is the right answer.
>
> Let the web application establish a session with the app server which
> corresponds with the web user's session. The app server does the query to
> the database server and can then send sections of the result set
> to the web
> app, as requested. If the web app goes away the app server times out the
> session and closes the query releasing all cached results. This does not
> cause the database server to do more than is reasonable for a
> database server.
>
>
>
>
> Community email addresses:
> Post message: IBDI@yahoogroups.com
> Subscribe: IBDI-subscribe@yahoogroups.com
> Unsubscribe: IBDI-unsubscribe@yahoogroups.com
> List owner: IBDI-owner@yahoogroups.com
>
> Shortcut URL to this page:
> http://www.yahoogroups.com/community/IBDI
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>