[
https://issues.apache.org/jira/browse/IGNITE-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966838#comment-14966838
]
Pavel Tupitsyn edited comment on IGNITE-1759 at 10/21/15 1:59 PM:
-------------------------------------------------------------------
2) We can check at startup whether Guid has expected layout and then choose
either a current faster approach, or a slower way through a Guid constructor.
was (Author: ptupitsyn):
1) Endianness does not matter here. Basically, we interpret a 16-byte memory
chunk as 2 ulongs and then reorder some bytes in them.
2) We can check at startup whether Guid has expected layout and then choose
either a current faster approach, or a slower way through a Guid constructor.
> .Net: Guid read/write is not platform-safe.
> -------------------------------------------
>
> Key: IGNITE-1759
> URL: https://issues.apache.org/jira/browse/IGNITE-1759
> Project: Ignite
> Issue Type: Bug
> Components: interop
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Fix For: 1.5
>
>
> Two problems here:
> 1) We do not count for endiannes, so byte shifts might be invalid.
> 2) Guid doesn't have fixed layout. For this reason there are no guarantees
> that it will take 16 bytes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
