> - "fat model" approach - put the db interaction in objects
If it's just DB interaction, then yes, in the object for sure.
> - put the db interactions in the conductor itself
There is a reasonable separation between using conductor for mechanics
(i.e. API deferring a long-running activity to co
On 02/18/2014 01:22 PM, Pitucha, Stanislaw Izaak wrote:
> Hi all,
> I'm writing some new code which uses objects sent around by rpc. I got to
> implementing some new conductor methods and started wondering... what's the
> current recommended way of interacting with the database? Many seem to be
> a
Hi all,
I'm writing some new code which uses objects sent around by rpc. I got to
implementing some new conductor methods and started wondering... what's the
current recommended way of interacting with the database? Many seem to be
around:
- "fat model" approach - put the db interaction in objects
