Re: Aggregates with dependencies
Willem van Gool <[email protected]>
| Newsgroups | gmane.comp.programming.domain-driven-design |
|---|---|
| Message-ID | <CAKqMafz8SJhGpVs8D_S71ZQHENbxe4qxrk7-ZB+anqWNOYxZMQ@mail.gmail.com> |
Greg, Dan, I'm with you on this. It sounds like a typical security/principal case where the security context is constructed by querying some authorization service. Other than that, once you have the necessary info, treat it is meta-data... On Fri, Feb 15, 2013 at 9:29 AM, Dan Haywood <[email protected]>wrote: > ** > > > +1 > > > On 15 February 2013 08:22, Greg Young <[email protected]> wrote: > >> >> >> I would add the user not as part of the event but as metadata describing >> the event. It is very common to include context information in metadata >> (such as security context or machine that did it etc). >> >> Greg >> >> >