You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2015/10/02 16:51:26 UTC
[jira] [Created] (IGNITE-1613) Platform .Net: Investigate
Guid/DateTime/String interoperability with Java
Pavel Tupitsyn created IGNITE-1613:
---------------------------------------
Summary: Platform .Net: Investigate Guid/DateTime/String interoperability with Java
Key: IGNITE-1613
URL: https://issues.apache.org/jira/browse/IGNITE-1613
Project: Ignite
Issue Type: Task
Components: interop
Affects Versions: ignite-1.5
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
Fix For: ignite-1.5
Currently in .Net we:
* write Guid and DateTime in Java format
* calculate string hash code for field names with Java algorithm on each call
Need to investigate if the following makes sense:
1) In .Net always write Guid and DateTime in native .Net format as fast as possible; Make Java understand that format. (Not every Guid written in .Net will be read in Java, so we can win time).
2) Cache string hashcodes somehow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)