Hello everybody,

I am porting a shared whiteboard from Microsoft.Ink.InkOverlay
to System.Windows.Controls.InkCanvas

Microsoft.Ink.Stroke had a property Id (unique identifier) that
I used to exactly identify the strokes that are to be deleted or
resized on remote copies of the InkCanvas. But
System.Windows.Ink .Stoke objects do NOT seem have such a
unique identifier assigned to them anymore...

Of course, I could always resend the entire Ink (serialized to ISF format)
to remote copies of an InkCanvas over the network: but that would take
far too much network capacity for my taste.

Thus I am now considering to re-implement the unique identifier
for System.Windows.Ink.Stroke objects by use of an attached property.

Does anyone more experienced than myself agree that this is indeed
what would be a reasonable approch to the problem of keeping distributed
copies of the same InkCanvas synchronized (as regards Ink it contains)?
Or is there some other solution that might seem preferable?
(In many cases, using the coordinates of the first point of a stroke could
serve as a unique identifier of that stroke, but I hesitate to use that kind
of hack just for the sake of "efficiency".)

Thanks in advance for any replies,
Christian