[
https://issues.apache.org/jira/browse/THRIFT-5010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16976397#comment-16976397
]
Edward Zhuravlov commented on THRIFT-5010:
------------------------------------------
(1) Yes. TBinaryProtocol need also read and write for integers number using
BinaryPrimitives. Network order for integers always Big Endian.
(2). Yes. But I'm newbie in this project. I have any questions about develop
technology: reference to packages on nuget.org is posible? If not, how can use
reference to System.Memory platform extension on netstandard 2.0?
(3). It improvement. Add potencial support for some processor architectures.
> NetStd: TFramedTransport - bigEndianConversion incorrect
> --------------------------------------------------------
>
> Key: THRIFT-5010
> URL: https://issues.apache.org/jira/browse/THRIFT-5010
> Project: Thrift
> Issue Type: Improvement
> Components: netstd - Library
> Affects Versions: 0.13.0
> Reporter: Edward Zhuravlov
> Priority: Major
> Labels: features
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> Conversion -should be- _from/to TCP protocol format (always big-Endian) to
> execution engine_ based on processor architecture. See System.BitConverter
> class ():
> [https://docs.microsoft.com/en-us/dotnet/api/system.bitconverter?view=netstandard-2.0]
> ??The endianness of an architecture is indicated by the
> [IsLittleEndian|https://docs.microsoft.com/en-us/dotnet/api/system.bitconverter.islittleendian?view=netframework-4.8]
> property, which returns {{true}} on little-endian systems and {{false}} on
> big-endian systems. On little-endian systems, lower-order bytes precede
> higher-order bytes. On big-endian system, higher-order bytes precede
> lower-order bytes. ??
> Recomended use BinaryPrimitives.WriteInt32BigEndian/ReadInt32BigEndian class
> from nuget System.Memory by Microsoft for NetStandard 2.0.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
