I would like to hear from others how do you model your transactions when
dealing to a simple one-to-many relationship transaction, as the classic
Sale and SaleItems case.

I've already seen one sending all data at once and others requesting first
the parent, retriving the created resource and then sending the childs (but
not in transaction).

How do you deal with this use case?

D. Reinert
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
Resteasy-users mailing list

Reply via email to