Bryan Duxbury wrote:
I feel that this suggestion is a bit of a red herring. Sure, you could
implement a tiny fraction of the Thrift library in C - maybe just the
protocol? - but then you'd still be stuck needing the full code generator
and a set of related language-specific tools. I'm thinking
On Aug 16, 2010, at 7:32 AM, Bryan Duxbury br...@rapleaf.com wrote:
On Sun, Aug 15, 2010 at 8:52 PM, Joe Schaefer joe_schae...@yahoo.comwrote:
Why not simply make that person a committer and let them hack on
trunk from the start?
I could agree with this in principle, but I think that
I feel like the git thing is pretty well solved already - we have a git
mirror of Thrift trunk, and for those who want to use git, that seems like
it works fine. I don't think it would make sense for us to *switch* all of
thrift to using git, though, if that's what you're suggesting.
On Mon, Aug
As someone who derives great benefit from Thrift and has advocated for it at
work, but hasn't participated in the community much, here are the things
that I'd love to see:
Easy Code Review Tool:
Patch files are a lousy way to review code (whether sent to the mailing list
or attached to a JIRA
Zitat von Joe Schaefer joe_schae...@yahoo.com:
- Original Message
From: Todd Lipcon t...@cloudera.com
To: thrift-dev@incubator.apache.org
Sent: Sun, August 15, 2010 1:24:09 PM
Subject: Re: sharing knowledge means sharing control
On Sun, Aug 15, 2010 at 12:58 PM, Joe Schaefer
- Original Message
From: ro...@bufferoverflow.ch ro...@bufferoverflow.ch
To: thrift-dev@incubator.apache.org
Sent: Sun, August 15, 2010 3:33:55 PM
Subject: Re: sharing knowledge means sharing control
Zitat von Joe Schaefer joe_schae...@yahoo.com:
- Original Message
On Sun, Aug 15, 2010 at 10:24 AM, Todd Lipcon t...@cloudera.com wrote:
A long time ago I proposed keeping a document around that classified each
language as stable, development, or unstable (or something to that
effect). The idea is that we'd accept any patch nearly blind for an
unstable
Todd Lipcon wrote:
. Moreover, Cassandra is a lot easier to accept patches
for, as it's a single-language project where most of the code is used by
most of the people, where Thrift is 15-language project where most people
use 20% of them.
If I may put in $0.02 - that is the main design
On Mon, Aug 16, 2010 at 1:01 AM, Mayan Moudgill ma...@bestweb.net wrote:
If I may put in $0.02 - that is the main design decisions which I wonder
about. Why not write the core in C and export the functions via wrappers to
each of the 15 languages? Among other things, this would enable any
Michael Walsh wrote:
On Mon, Aug 16, 2010 at 1:01 AM, Mayan Moudgill ma...@bestweb.net wrote:
If I may put in $0.02 - that is the main design decisions which I wonder
about. Why not write the core in C and export the functions via wrappers to
each of the 15 languages? Among other things,
- Original Message
From: Aron Sogor big...@gmail.com
To: thrift-dev@incubator.apache.org
Sent: Sun, August 15, 2010 11:43:59 PM
Subject: Re: sharing knowledge means sharing control
Joe,
To be clear: forks or branches for this discussion sake is the same
thing, a copy
THRIFT-819 to me is a pattern of dialog I'd like
to see improved. Too often I see issues filed
in Thrift's jira that get turned down by Facebook
folks without any input from non-Facebook committers.
That tends to institutionalize the idea Facebook
retains tight control over all architectural
Too often I see issues filed
in Thrift's jira that get turned down by Facebook
folks without any input from non-Facebook committers.
One way to resolve this is for the Facebook employees
to continue to comment on these issues but to ask for
input from other committers before closing the
On Sat, Aug 14, 2010 at 12:25 PM, Joe Schaefer joe_schae...@yahoo.comwrote:
THRIFT-819 to me is a pattern of dialog I'd like
to see improved. Too often I see issues filed
in Thrift's jira that get turned down by Facebook
folks without any input from non-Facebook committers.
That tends to
14 matches
Mail list logo
