Hi Tim

Are there plans to add support for more extensive client-side buffering?
For example, having the ability to do finds and set ranges without a trip to
the server if the required records are sitting in the RemoteReadSize cache.

Rob

Rob,

<< Are there plans to add support for more extensive client-side buffering?
For example, having the ability to do finds and set ranges without a trip to
the server if the required records are sitting in the RemoteReadSize cache.
>>

Well, such a scenario will most likely evolve from the cached updates
functionality, when it is added.  The main reason why it isn't added to
"normal" operation is because it would cause the local and remote sessions
to behave differently.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tim

> The main reason why it isn't added to "normal" operation is because it
> would cause the local and remote sessions to behave differently.
>

If RemoteReadSize cache is being used, aren't they already behaving
differently?

Rob

Rob,

<< If RemoteReadSize cache is being used, aren't they already behaving
differently? >>

Yes, but only in a very minor way that wouldn't be noticeable.  The cache
only works in the cases where absolute navigation does not take place,
therefore it is simply used for situations where a prior/next type of
navigation takes place in a repetitive fashion, and on the same small area
of the dataset.

--
Tim Young
Elevate Software
www.elevatesoft.com