You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@thrift.apache.org by Apache Wiki <wi...@apache.org> on 2010/08/16 21:36:52 UTC

[Thrift Wiki] Update of "LanguageSupport" by RogerMeier

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 || || || || || ||

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by Michael Greene <mi...@gmail.com>.
I was worried about all the ?s when I originally chose not to link it from
the front page.  It would be great if more details were added to several of
the library implementations.

Michael

On Mon, Aug 16, 2010 at 4:44 PM, Anthony Molinaro <
anthonym@alumni.caltech.edu> wrote:

> Nice, I guess it needs to be updated, and maybe this should be on the
> main page of the wiki (and maybe on the main web page as well)?  Just
> seems like good information to have when deciding to use thrift, but
> seems to be buried.
>
> -Anthony
>
> On Mon, Aug 16, 2010 at 01:00:00PM -0700, David Reiss wrote:
> > 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 || || || || || ||
>
> --
> ------------------------------------------------------------------------
> Anthony Molinaro                           <an...@alumni.caltech.edu>
>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by Anthony Molinaro <an...@alumni.caltech.edu>.
Nice, I guess it needs to be updated, and maybe this should be on the
main page of the wiki (and maybe on the main web page as well)?  Just
seems like good information to have when deciding to use thrift, but
seems to be buried.

-Anthony

On Mon, Aug 16, 2010 at 01:00:00PM -0700, David Reiss wrote:
> 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 || || || || || ||

-- 
------------------------------------------------------------------------
Anthony Molinaro                           <an...@alumni.caltech.edu>

RE: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by James King <Ja...@Dell.com>.
Sorry guys, just trying to promote it and get things moving on it.  If
you feel it doesn't belong there then remove it.  I posted about the
stuff a while back but there was very little interest at the time
because there was no accompanying code.  I'll try to factor out some
personal time to port this over to Java and then C++ so we have a patch
for at least three of the languages.

-----Original Message-----
From: Michael Greene [mailto:michael.greene@gmail.com] 
Sent: Wednesday, August 18, 2010 5:43 PM
To: thrift-dev@incubator.apache.org
Subject: Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

THRIFT-66 is a bit of an odd case for that page, since it is something
just recently put forward and has a large scope, large enough that there
has been no evaluation yet.  I agree that if we're putting patch numbers
in, we should link them -- I have done this for the few in the table
already.

Michael

On Wed, Aug 18, 2010 at 4:32 PM, Anthony Molinaro <
anthonym@alumni.caltech.edu> wrote:

> In that case should THRIFT-66 be listed at all.  It seems like maybe 
> that patch is too big and contains too many things, so it's unlikely 
> to be applied without quite a bit more discussion, so maybe we don't 
> list it at all?
> Also, I wonder if it's worth it to have patches actually link to the 
> jira tickets?
>
> -Anthony
>
> On Wed, Aug 18, 2010 at 11:16:07PM +0200, roger@bufferoverflow.ch
wrote:
> > I think we should not add a seperate column for 2-way and 
> > multiplexing at the moment.
> >
> > This topic was not discussed in deep within the community and it is 
> > very important to align such things with the high level architecture

> > and design concepts.
> >
> > Otherwise we run probably into very bad compatibility issues between

> > the languages and multiplexing vs. non-multiplexing, etc.
> >
> > -Roger
> >
> >
> >
> > Quoting Anthony Molinaro <an...@alumni.caltech.edu>:
> >
> > >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,
roger@bufferoverflow.chwrote:
> > >>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 < 
> > >>>anthonym@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 < 
> > >>>>> anthonym@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,
> > >>>>roger@bufferoverflow.chwrote:
> > >>>>> > > ok, I did not know that.
> > >>>>> > >
> > >>>>> > > I'm ready to merge them, but which one should we keep?
> > >>>>> > >
> > >>>>> > > Quoting David Reiss <dr...@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, 
> > >>>>> > > >>|| C++ || 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                           <
> > >>>>anthonym@alumni.caltech.edu>
> > >>>>> >
> > >>>>
> > >>>>--
> >
> >>>>------------------------------------------------------------------
> >>>>------
> > >>>>Anthony Molinaro                           <
> anthonym@alumni.caltech.edu>
> > >>>>
> > >>>
> > >>
> > >>
> > >>
> > >>----------------------------------------------------------------
> > >>This message was sent using IMP, the Internet Messaging Program.
> > >>
> > >
> > >--
> >
>-----------------------------------------------------------------------
-
> > >Anthony Molinaro
<anthonym@alumni.caltech.edu
> >
> > >
> > >
> > >
> >
> >
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
>
> --
>
------------------------------------------------------------------------
> Anthony Molinaro
<an...@alumni.caltech.edu>
>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by Michael Greene <mi...@gmail.com>.
THRIFT-66 is a bit of an odd case for that page, since it is something just
recently put forward and has a large scope, large enough that there has been
no evaluation yet.  I agree that if we're putting patch numbers in, we
should link them -- I have done this for the few in the table already.

Michael

On Wed, Aug 18, 2010 at 4:32 PM, Anthony Molinaro <
anthonym@alumni.caltech.edu> wrote:

> In that case should THRIFT-66 be listed at all.  It seems like maybe that
> patch is too big and contains too many things, so it's unlikely to be
> applied
> without quite a bit more discussion, so maybe we don't list it at all?
> Also, I wonder if it's worth it to have patches actually link to the
> jira tickets?
>
> -Anthony
>
> On Wed, Aug 18, 2010 at 11:16:07PM +0200, roger@bufferoverflow.ch wrote:
> > I think we should not add a seperate column for 2-way and multiplexing
> > at the moment.
> >
> > This topic was not discussed in deep within the community and it is
> > very important to align such things with the high level architecture
> > and design concepts.
> >
> > Otherwise we run probably into very bad compatibility issues between
> > the languages and multiplexing vs. non-multiplexing, etc.
> >
> > -Roger
> >
> >
> >
> > Quoting Anthony Molinaro <an...@alumni.caltech.edu>:
> >
> > >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, roger@bufferoverflow.chwrote:
> > >>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 <
> > >>>anthonym@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 <
> > >>>>> anthonym@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,
> > >>>>roger@bufferoverflow.chwrote:
> > >>>>> > > ok, I did not know that.
> > >>>>> > >
> > >>>>> > > I'm ready to merge them, but which one should we keep?
> > >>>>> > >
> > >>>>> > > Quoting David Reiss <dr...@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                           <
> > >>>>anthonym@alumni.caltech.edu>
> > >>>>> >
> > >>>>
> > >>>>--
> >
> >>>>------------------------------------------------------------------------
> > >>>>Anthony Molinaro                           <
> anthonym@alumni.caltech.edu>
> > >>>>
> > >>>
> > >>
> > >>
> > >>
> > >>----------------------------------------------------------------
> > >>This message was sent using IMP, the Internet Messaging Program.
> > >>
> > >
> > >--
> > >------------------------------------------------------------------------
> > >Anthony Molinaro                           <anthonym@alumni.caltech.edu
> >
> > >
> > >
> > >
> >
> >
> >
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> >
>
> --
> ------------------------------------------------------------------------
> Anthony Molinaro                           <an...@alumni.caltech.edu>
>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by Anthony Molinaro <an...@alumni.caltech.edu>.
In that case should THRIFT-66 be listed at all.  It seems like maybe that
patch is too big and contains too many things, so it's unlikely to be applied
without quite a bit more discussion, so maybe we don't list it at all?
Also, I wonder if it's worth it to have patches actually link to the
jira tickets?

-Anthony

On Wed, Aug 18, 2010 at 11:16:07PM +0200, roger@bufferoverflow.ch wrote:
> I think we should not add a seperate column for 2-way and multiplexing  
> at the moment.
> 
> This topic was not discussed in deep within the community and it is  
> very important to align such things with the high level architecture  
> and design concepts.
> 
> Otherwise we run probably into very bad compatibility issues between  
> the languages and multiplexing vs. non-multiplexing, etc.
> 
> -Roger
> 
> 
> 
> Quoting Anthony Molinaro <an...@alumni.caltech.edu>:
> 
> >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, roger@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 <
> >>>anthonym@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 <
> >>>>> anthonym@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,
> >>>>roger@bufferoverflow.chwrote:
> >>>>> > > ok, I did not know that.
> >>>>> > >
> >>>>> > > I'm ready to merge them, but which one should we keep?
> >>>>> > >
> >>>>> > > Quoting David Reiss <dr...@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                           <
> >>>>anthonym@alumni.caltech.edu>
> >>>>> >
> >>>>
> >>>>--
> >>>>------------------------------------------------------------------------
> >>>>Anthony Molinaro                           <an...@alumni.caltech.edu>
> >>>>
> >>>
> >>
> >>
> >>
> >>----------------------------------------------------------------
> >>This message was sent using IMP, the Internet Messaging Program.
> >>
> >
> >--
> >------------------------------------------------------------------------
> >Anthony Molinaro                           <an...@alumni.caltech.edu>
> >
> >
> >
> 
> 
> 
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> 

-- 
------------------------------------------------------------------------
Anthony Molinaro                           <an...@alumni.caltech.edu>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by ro...@bufferoverflow.ch.
I think we should not add a seperate column for 2-way and multiplexing  
at the moment.

This topic was not discussed in deep within the community and it is  
very important to align such things with the high level architecture  
and design concepts.

Otherwise we run probably into very bad compatibility issues between  
the languages and multiplexing vs. non-multiplexing, etc.

-Roger



Quoting Anthony Molinaro <an...@alumni.caltech.edu>:

> 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, roger@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 <
>> >anthonym@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 <
>> >>> anthonym@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,
>> >>roger@bufferoverflow.chwrote:
>> >>> > > ok, I did not know that.
>> >>> > >
>> >>> > > I'm ready to merge them, but which one should we keep?
>> >>> > >
>> >>> > > Quoting David Reiss <dr...@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                           <
>> >>anthonym@alumni.caltech.edu>
>> >>> >
>> >>
>> >>--
>> >>------------------------------------------------------------------------
>> >>Anthony Molinaro                           <an...@alumni.caltech.edu>
>> >>
>> >
>>
>>
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>
>
> --
> ------------------------------------------------------------------------
> Anthony Molinaro                           <an...@alumni.caltech.edu>
>
>
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by Anthony Molinaro <an...@alumni.caltech.edu>.
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, roger@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 <
> >anthonym@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 <
> >>> anthonym@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, 
> >>roger@bufferoverflow.chwrote:
> >>> > > ok, I did not know that.
> >>> > >
> >>> > > I'm ready to merge them, but which one should we keep?
> >>> > >
> >>> > > Quoting David Reiss <dr...@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                           <
> >>anthonym@alumni.caltech.edu>
> >>> >
> >>
> >>--
> >>------------------------------------------------------------------------
> >>Anthony Molinaro                           <an...@alumni.caltech.edu>
> >>
> >
> 
> 
> 
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> 

-- 
------------------------------------------------------------------------
Anthony Molinaro                           <an...@alumni.caltech.edu>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by ro...@bufferoverflow.ch.
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 <
> anthonym@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 <
>> > anthonym@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, roger@bufferoverflow.chwrote:
>> > > > ok, I did not know that.
>> > > >
>> > > > I'm ready to merge them, but which one should we keep?
>> > > >
>> > > > Quoting David Reiss <dr...@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                           <
>> anthonym@alumni.caltech.edu>
>> > >
>>
>> --
>> ------------------------------------------------------------------------
>> Anthony Molinaro                           <an...@alumni.caltech.edu>
>>
>



----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.


Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by 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 <
anthonym@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 <
> > anthonym@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, roger@bufferoverflow.chwrote:
> > > > ok, I did not know that.
> > > >
> > > > I'm ready to merge them, but which one should we keep?
> > > >
> > > > Quoting David Reiss <dr...@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                           <
> anthonym@alumni.caltech.edu>
> > >
>
> --
> ------------------------------------------------------------------------
> Anthony Molinaro                           <an...@alumni.caltech.edu>
>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by Anthony Molinaro <an...@alumni.caltech.edu>.
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 <
> anthonym@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, roger@bufferoverflow.ch wrote:
> > > ok, I did not know that.
> > >
> > > I'm ready to merge them, but which one should we keep?
> > >
> > > Quoting David Reiss <dr...@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                           <an...@alumni.caltech.edu>
> >

-- 
------------------------------------------------------------------------
Anthony Molinaro                           <an...@alumni.caltech.edu>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by Bryan Duxbury <br...@rapleaf.com>.
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 <
anthonym@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, roger@bufferoverflow.ch wrote:
> > ok, I did not know that.
> >
> > I'm ready to merge them, but which one should we keep?
> >
> > Quoting David Reiss <dr...@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                           <an...@alumni.caltech.edu>
>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by Anthony Molinaro <an...@alumni.caltech.edu>.
I sort of like the one with the pretty colors :)

-Anthony

On Tue, Aug 17, 2010 at 08:34:40AM +0200, roger@bufferoverflow.ch wrote:
> ok, I did not know that.
> 
> I'm ready to merge them, but which one should we keep?
> 
> Quoting David Reiss <dr...@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                           <an...@alumni.caltech.edu>

Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by ro...@bufferoverflow.ch.
ok, I did not know that.

I'm ready to merge them, but which one should we keep?

Quoting David Reiss <dr...@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.


Re: [Thrift Wiki] Update of "LanguageSupport" by RogerMeier

Posted by David Reiss <dr...@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 || || || || || ||