Hi there

I'm working on a project which heavily depends on a typed datasets - winform clients retrieve them from webservices, users perform some work on them, and they are returned to the webservice which updates the DB based on a dataset state.

I'm wondering how could I migrate with this architecture to LLBLGEN. What would be the equivalent to the dataset - a container of different datatables that I can conveniently pass as an argument (and bind to it using differenet datamembers to differenet bindingsources)?

thanks a lot

Hi mrm,

I recommend you to read this WebServices and WCF section of the manual to know your options.

daelmo wrote:

Hi mrm,

I recommend you to read this WebServices and WCF section of the manual to know your options.

Hi

Thanks for the suggestion. I've read it already, but it doesn't really answer my question - I wasn't concerned about the serialization techniques but rather about a way to pass many kinds of entities in one request. Eg. the example contains a webservice with GetCustomers webmethod - that means, that for each form I should make as many requests as many kinds of entities I use on the form, while with a dataset I could send all those related entities in one go (customers, orders, employees etc.).

Does LLBLGEN provide such container? What is a practice of dealing with such situations? I know that with a web app you could just send it one by one, but I don't think it's a sensible option with a webservices and low-bandwidth connected clients, is it?

thanks for any ideas mrm

Hi there.

mrn wrote:

while with a dataset I could send all those related entities in one go (customers, orders, employees etc.)

I don't think it works that way, the plumbing is always updating table by table.

There exist UnitOfWork, though WCF can't use unitofwork, it's not serializable to XML.

You can pass DTO objects to the service and at server-side perform the needed actions.