So should the 2-way communication and service multiplexing maybe be a separate column? I'm not sure of the exact implementation but looking at the bug it seems like some of it is new clients and servers, so maybe instead of the additional note on thrift-66 we have some new columns for multiplexed client and multiplexed server?
-Anthony On Wed, Aug 18, 2010 at 10:28:11PM +0200, ro...@bufferoverflow.ch wrote: > I've merged the two pages and added an additional color: > orange => patch available > > LanguageSupport page is now redirected to > http://wiki.apache.org/thrift/LibraryFeatures > > Zitat von Bryan Duxbury <br...@rapleaf.com>: > > >I think we only need done (green), planned (yellow), won't fix (red), and > >unknown (white). > > > >On Tue, Aug 17, 2010 at 11:21 AM, Anthony Molinaro < > >antho...@alumni.caltech.edu> wrote: > > > >>Sounds good to me. How would you use the colors? Green probably means > >>complete/stable, yellow could mean experimental, red could mean > >>not implemented, white is still unknown (although we should try to > >>categorize all the white ones with this exercise), orange is planned? > >>This is mostly what is there now, except that yellow and red have > >>different > >>meanings. > >> > >>-Anthony > >> > >>On Tue, Aug 17, 2010 at 10:05:05AM -0700, Bryan Duxbury wrote: > >>> I agree that we should keep the older version, but I think it needs more > >>> than a little bit of love. I'd say keep the colors, but instead of T/F/? > >>> values in the table, I think we should put version numbers. In the case > >>of > >>> completed stuff, the version number would mean "since"; for planned > >>stuff, > >>> it would mean "planned for". > >>> > >>> Thoughts? > >>> > >>> On Tue, Aug 17, 2010 at 9:40 AM, Anthony Molinaro < > >>> antho...@alumni.caltech.edu> wrote: > >>> > >>> > I sort of like the one with the pretty colors :) > >>> > > >>> > -Anthony > >>> > > >>> > On Tue, Aug 17, 2010 at 08:34:40AM +0200, > >>ro...@bufferoverflow.chwrote: > >>> > > ok, I did not know that. > >>> > > > >>> > > I'm ready to merge them, but which one should we keep? > >>> > > > >>> > > Quoting David Reiss <dre...@facebook.com>: > >>> > > > >>> > > >We already have something like this at > >>> > > >http://wiki.apache.org/thrift/LibraryFeatures > >>> > > >but it's a huge pain to edit. > >>> > > > > >>> > > >On 08/16/2010 12:36 PM, Apache Wiki wrote: > >>> > > >>Dear Wiki user, > >>> > > >> > >>> > > >>You have subscribed to a wiki page or wiki category on "Thrift > >>> > > >>Wiki" for change notification. > >>> > > >> > >>> > > >>The "LanguageSupport" page has been changed by RogerMeier. > >>> > > >>http://wiki.apache.org/thrift/LanguageSupport > >>> > > >> > >>> > > >>-------------------------------------------------- > >>> > > >> > >>> > > >>New page: > >>> > > >>This Page describes the supported protocol, transport and server > >>> > > >>types for each Language > >>> > > >>|| '''Language''' || '''Maturity Level''' || '''Protocol Types''' > >>> > > >>|| '''Transport Types''' || '''Server Types''' || > >>'''Description''' > >>> > > >>|| > >>> > > >>|| C++ || widely used || Binary, json || buffered, framed, http || > >>> > > >>simple, thread-pool, threaded, nonblocking|| || > >>> > > >>|| C# || || || || || || > >>> > > >>|| Erlang || || || || || || > >>> > > >>|| Haskell || || || || || || > >>> > > >>|| Java || || || || || || > >>> > > >>|| JavaScript || new in 0.3 || json|| http || none || || > >>> > > >>|| Objective C/Cocoa || || || || || || > >>> > > >>|| OCaml || || || || || || > >>> > > >>|| Perl || || || || || || > >>> > > >>|| PHP || || || || || || > >>> > > >>|| Python || || || || || || > >>> > > >>|| Ruby || || || || || || > >>> > > >>|| Squeak || || || || || || > >>> > > > > >>> > > > > >>> > > > > >>> > > > >>> > > > >>> > > > >>> > > ---------------------------------------------------------------- > >>> > > This message was sent using IMP, the Internet Messaging Program. > >>> > > > >>> > > >>> > -- > >>> > > >>------------------------------------------------------------------------ > >>> > Anthony Molinaro < > >>antho...@alumni.caltech.edu> > >>> > > >> > >>-- > >>------------------------------------------------------------------------ > >>Anthony Molinaro <antho...@alumni.caltech.edu> > >> > > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > -- ------------------------------------------------------------------------ Anthony Molinaro <antho...@alumni.caltech.edu>
