军情直播间 歼-11B南海挂弹飞行 挑战陌生海空环境
Current License: CC BY-SA 4.0
6 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jul 14 at 20:23 | vote | accept | Axo | ||
Jul 14 at 19:10 | history | closed |
Roddy of the Frozen Peas TylerH Eugene S. |
Opinion-based | |
Jul 14 at 17:48 | comment | added | Chris | This is opinion - there is no 'best' design. But your options are not mutually exclusive. You can accept a Container endpoint that operates on container DTOs and handle the collection of elements in that DTO how ever you want - even cascading the merge/persist /delete options as required. (ie orphan removal can clean up de-referenced Element instances, but that isn't a good one if you want them to exist on their own or be moved around). You could also have individual element endpoints that accept Element DTOs and change their collections through that | |
Jul 13 at 12:13 | answer | added | Karmelina Michael | timeline score: 2 | |
Jul 11 at 17:26 | review | Close votes | |||
Jul 14 at 19:10 | |||||
Jul 11 at 16:48 | history | asked | Axo | CC BY-SA 4.0 |