[
https://issues.apache.org/jira/browse/IGNITE-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15134354#comment-15134354
]
Pavel Tupitsyn edited comment on IGNITE-1563 at 2/5/16 3:57 PM:
----------------------------------------------------------------
1) I was wrong. Batch size does not incur network trips. It is a direct field
write in Java, same as DataStreamer properties. This fits guidelines quite well.
I was thinking about turning read/write pair into a property, and this
certainly is not correct. But BatchSize should be a property, fixed.
2) We need that because user can override Equals/GetHashCode.
There is no keepBinary flag in AtomicReference. And comparison callback with
keepBinary flag does not make sense, me might as well compare binary objects on
Java side.
3) Fixed
was (Author: ptupitsyn):
1) I was wrong. Batch size does not incur network trips. It is a direct field
write in Java, same as DataStreamer properties. This fits guidelines quite well.
I was thinking about turning read/write pair into a property, and this
certainly is not correct. But BatchSize should be a property, fixed.
> .Net: Implement "atomic" data structures.
> -----------------------------------------
>
> Key: IGNITE-1563
> URL: https://issues.apache.org/jira/browse/IGNITE-1563
> Project: Ignite
> Issue Type: Task
> Components: platforms
> Affects Versions: 1.5.0.final
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Fix For: 1.6
>
>
> This includes:
> atomicSequence;
> atomicStamped;
> atomicReference
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
