> 2. If the team doesn't like the reference counting scheme we could also use a create/copy/release scheme (possibly with copy-on-write semantics for efficiency, but copying is probably not a problem for the current use cases).
The goal of this scheme (and the ref/unref scheme) is to make MirPlatformMessage an object that is useful to the client outside the strict context of the platform operation call and callback. If we don't need/want this then we could just make it a simple container that the user must extract/acquire data from as discussed in the call.
> 2. If the team doesn't like the reference counting scheme we could also use a create/copy/release scheme (possibly with copy-on-write semantics for efficiency, but copying is probably not a problem for the current use cases).
The goal of this scheme (and the ref/unref scheme) is to make MirPlatformMessage an object that is useful to the client outside the strict context of the platform operation call and callback. If we don't need/want this then we could just make it a simple container that the user must extract/acquire data from as discussed in the call.