All of this I understand, but what I'm asking is this...
ex. client application fetches 1(one) row the server, the server sends over
10 rows. These rows are now batched on the client side (by the client side
Firebird/Interbase components/DLL). Now when the client requests another
row, that row is pulled from the client side buffer(maintained by the client
side FB/IB components/DLL). New data is requested from the server when the
rows in the client side buffers are exhausted. This type of implementation
is used by some of the big databases.

But from your answer I guess FB/IB does not support this.

Thanks

-----Original Message-----
From: alex_vnru [mailto:ded@...]
Sent: Tuesday, April 23, 2002 12:38 AM
To: ib-support@yahoogroups.com
Subject: [ib-support] Re: Client-Side buffers

--- In ib-support@y..., "Reggie White" <reggiewhite@l...> wrote:
> Are there any settings or anything that I can do to inform Firebird
approx.
> how many records to send across the wire per Fetch?
>
> I know some database will send 10+ record across the wire per Server
fetch
> and then the client works from the records in its buffers until they
are
> exhausted and request another batch of records from the Server.

Reggie, fetch in Firebird is controlled by client. If you use
non-buffering client-side component, theoretically it receive one row,
buffering components get rows by own demand. But since there is one
more buffering section in the chain - network protocol - in practice
client COMPUTER (not application) get at once one or two network
packets.

Best regards, Alexander V.Nevsky.



To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/