[bug_rejected] How to cut ZDataSet into two?

[zsoca]

Your ZeosLib DBO Version: 6.5.1
The IDE you are using: Delphi
Version (and maybe patchlevel) of the IDE:
The database you are using: Firebird
Version of the database: 2.0
Used protocol: tcp/ip
[hr]Error description and post

Hi friends!

I am interested in cutting the ZDataSet into two parts, and connecting them with a middleware/rpc layer.
On the server side I would like to have the data retreival part. It would fill the internal buffer based in the SQL and the params, and send the data to the client. The client gives the data to the data aware components, and does the data request and update.
I would like to get some help on how could I separate these concerns into two components.
Any ideas are welcome...

Best regards, Zsolt Balanyi

P.S.: I made it with Multi-Master datasets, so I hope this will work too!

[mdaems]

Hi Zsolt,

As far as I know this is not to be done the Dataset level. The datasource classes are between the dataset and the components. If you want to split you should have a look at the TDatabroker components. I never used them. I don't know what they can or can not, but according to the documentation that's what they are designed for.

If you want more help from other users you better post this kind of questions in the general forum for 6. This feature request is denied (unless you have more specific details).

Mark

[zsoca]

Hi!

There are TDatabroker components, you are right. The problem is that they do not transport the data in the native (buffer) format, but they do a transformation, which is quite time-consuming. In order to achieve better performance I need to split the native component itself...
I can do it myself, no need to itsomeone else! I just needed a few pieces of advice, how and where to break the component up.

Best regards, Zsolt Balanyi