I think this veers off into territory that should be avoided for this project.
I am not against having coding standards. Not at all. But Thrift is a fairly
mature product. Disregarding new language support, I suspect that the bulk of
the future coding required will be bug fixes. If that is
[
https://issues.apache.org/jira/browse/THRIFT-1260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rush Manbert updated THRIFT-1260:
-
Attachment: thrift-fix-csharp-http-client-hang.patch
We got the same error using the latest
Hi All,
I need to do something that uses both the latest and greatest Thrift compiler
and our older version.
Our IDL files work with the latest compiler except when we try to set a default
value for a struct member by specifying an enum value. With the old compiler
you just used the enum's
WITH the prefix.
-Ursprüngliche Nachricht- From: Rush Manbert
Sent: Wednesday, May 14, 2014 6:27 PM
To: dev@thrift.apache.org
Subject: Can anyone point me to the JIRA for this compiler feature?
Hi All,
I need to do something that uses both the latest and greatest Thrift
compiler and our
Hi Sachith,
I would define a thrift struct that has metadata about the file, followed by a
member of type listbyte that stores the file data. I would also define the
metadata so it can support transmitting the file in chunks (data that says this
is chunk m of n, for instance), where each chunk
Ah, good to know. Thanks.
On Mar 5, 2014, at 2:40 PM, Ben Craig wrote:
Don't use listbyte. Large list performance is pretty bad, because
elements tend to be serialized one at a time. Use 'binary' or 'string'
instead. You also get significantly fewer copies this way.
Rush Manbert r
On Jul 11, 2012, at 9:48 PM, Bert Douglas wrote:
I am using the same message schema, or thrift file in c++ and in erlang.
Also setting same three fields in a large struct/record.
Looking at network with wireshark.
Erlang client sends this:
004080 01 00 01 00 00 00 06 64 65 74 65
I asked this question more than 18 months ago on the users list and never got
an answer, so I'm trying again here.
We check in our Thrift IDL (*.thrift) files and when we do builds on the Mac,
those files are read and the code for different languages is generated. We also
check in the
The Wikipedia article here:
http://en.wikipedia.org/wiki/Apache_Thrift
says this:
TMemoryTransport – Uses memory for I/O. The Java implementation uses a simple
ByteArrayOutputStream internally.
I am currently interested in a memory-based transport for a very specialized
application. I
[
https://issues.apache.org/jira/browse/THRIFT-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13024965#comment-13024965
]
Rush Manbert commented on THRIFT-591:
-
Carl is correct in general. If the patch were
10 matches
Mail list logo