Context Navigation

Warning: Can't synchronize with repository "(default)" (/home/git/ome.git does not appear to be a Git repository.). Look in the Trac log for more information.

Changes between Version 1 and Version 2 of Ticket #11532, comment 38

Timestamp:: 11/27/15 12:28:25 (8 years ago)
Author:: mtbcarroll
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #11532, comment 38

v1	v2
3	3	However, it helps us to fix `PixelsImpl` rather less than I'd originally hoped: pixels need an image and channels need a pixels so they have to be duplicated attached to other things, and they also link via other model objects to detectors and instruments and stuff, so if any of those are to be duplicated then the whole set should probably be in the same operation, yet the pixels service offers ability to mess with the pixels object and its channels and whatnot, and to create extra pixels on the original image, so a whole subgraph duplicate isn't what's really wanted.
4	4
5		To avoid multiply duplicating subgraph fragments through reaching them via required properties from different objects that do need duplicating, it might actually be easier to duplicate the whole lot then delete / graft as appropriate. (For instance, to delete channels not in the provided `channelList`.) However, that requires addition of a `DeleteMessage` and yet more transactions (I assume we can't move `PixelsImpl` to Blitz), and pretty much a reimplementation of the pixels service.
	5	To avoid multiply duplicating subgraph fragments through reaching them via required properties from different objects that do need duplicating, it might actually be easier to duplicate the whole lot then delete or graft as appropriate. (For instance, to delete channels not in the provided `channelList`.) However, that requires addition of a `DeleteMessage` and yet more transactions (I assume we can't move `PixelsImpl` to Blitz), and pretty much a reimplementation of the pixels service.
6	6
7	7	I'm thus tempted to push this again, I'm afraid; I hadn't realized how awkwardly featureful the pixels service is. I wonder how well our integration testing covers those features.