thrift-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Hammerbacher <ham...@cloudera.com>
Subject Re: question about using one transport in both directions
Date Mon, 04 May 2009 16:53:18 GMT
Hey Yordan,

1) Check out http://thrift.markmail.org to search the thrift mailing lists.
2) It seems like http://wiki.apache.org/thrift/LibraryFeatures is a start
for what you're looking to see on the wiki. Given that it is a wiki, you
could help fill out the documentation with a skeleton of what you're
requesting, perhaps filling in some of it yourself.

Later,
Jeff

On Mon, May 4, 2009 at 3:51 AM, Yordan Pavlov <y.d.pavlov@gmail.com> wrote:

> Thanks for the help. The thirft community seems to be pretty helpful.
> However I want to stress everyone's attention on the fact that
> Thrift's documentation is hard to access and not well structured. As
> new users come around the mailing lists will get bloated with the same
> basic questions which everyone would have. I am not pretty sure what
> the hierarchy in the community is and who should initiate such an
> activity but I believe that the following should be done:
>
> 1) The mailing list archive should be searchable. Starting a forum
> might be even a better idea since it can structure the topics in
> sections.
> 2) The different libraries, their pros and cons and their api should
> be described in the wiki. I think the wiki format is best for this
> purpose so that the community can easily edit errors and improvements
> as they appear.
>
> On Tue, Apr 28, 2009 at 9:29 PM, Joel Meyer <joel.meyer@gmail.com> wrote:
> >
> > There was a thread called "Using thrift as part of a game network
> protocol"
> > that dealt with a similar issue:
> >
> > Thread start (in March):
> >
> http://mail-archives.apache.org/mod_mbox/incubator-thrift-user/200903.mbox/%3cfba570180903222254u61876853o7daed3fee53f8db@mail.gmail.com%3e
> >
> > Thread continue (in April):
> >
> http://mail-archives.apache.org/mod_mbox/incubator-thrift-user/200904.mbox/%3c5e50457d0904021617x2056785dq1b7ed074e3919bf0@mail.gmail.com%3e
> >
> > In short (and it's nowhere near being a 'best practice') you could
> achieve
> > this using all 'oneway void' messages if you're willing to move the
> blocking
> > from the protocol layer into your application layer (or design your app
> to
> > use async calls).
> >
> > Hope that helps,
> > Joel
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message