requirements for a new release (was Re: java and twisted python compatibility?)

[Esteve Fernandez <es...@sindominio.net>]

Hi

> On Thu, Nov 5, 2009 at 2:09 PM, Esteve Fernandez <es...@sindominio.net>
> wrote:
>> I'd be in favor of deprecating the non-framed transports, it's a bit weird
>> that developers have to foresee whether their servers will be accessed by
>> framed or non-framed clients.
>
> +1

Good :-) Given that it's seems reasonable to make the framed transport as the
default one, what do you guys think of marking it as a requirement for
officially support a language and making a new release (which we should do
ASAP)? We're already making some progress towards that, but maybe we should
have a list of what we want to ship.

The list of languages that support framed transports is, so far:

- C++
- Java
- Erlang
- Ruby
- Perl
- Python

support for C# is not committed yet, but Michael gave his approval to this:

http://issues.apache.org/jira/browse/THRIFT-210

Cheers.

Re: requirements for a new release (was Re: java and twisted python compatibility?)

[Chris Goffinet <go...@digg.com>]

+1

I'd be in favor of seeing this as well.

-Chris

On Nov 7, 2009, at 2:51 PM, Chad Walters wrote:

> Sounds like a good idea to me.
>
> Seems like PHP should be on that list too:
> http://svn.apache.org/viewvc/incubator/thrift/trunk/lib/php/src/transport/TFramedTransport.php?revision=760189&view=markup
>
> Chad
>
> -----Original Message-----
> From: Esteve Fernandez [mailto:esteve@sindominio.net]
> Sent: Thursday, November 05, 2009 6:30 PM
> To: thrift-dev@incubator.apache.org
> Subject: requirements for a new release (was Re: java and twisted  
> python compatibility?)
>
> Hi
>
>> On Thu, Nov 5, 2009 at 2:09 PM, Esteve Fernandez <esteve@sindominio.net 
>> >
>> wrote:
>>> I'd be in favor of deprecating the non-framed transports, it's a  
>>> bit weird
>>> that developers have to foresee whether their servers will be  
>>> accessed by
>>> framed or non-framed clients.
>>
>> +1
>
> Good :-) Given that it's seems reasonable to make the framed  
> transport as the
> default one, what do you guys think of marking it as a requirement for
> officially support a language and making a new release (which we  
> should do
> ASAP)? We're already making some progress towards that, but maybe we  
> should
> have a list of what we want to ship.
>
> The list of languages that support framed transports is, so far:
>
> - C++
> - Java
> - Erlang
> - Ruby
> - Perl
> - Python
>
> support for C# is not committed yet, but Michael gave his approval  
> to this:
>
> http://issues.apache.org/jira/browse/THRIFT-210
>
> Cheers.
>

RE: requirements for a new release (was Re: java and twisted python compatibility?)

[Chad Walters <Ch...@microsoft.com>]

Sounds like a good idea to me.

Seems like PHP should be on that list too:
http://svn.apache.org/viewvc/incubator/thrift/trunk/lib/php/src/transport/TFramedTransport.php?revision=760189&view=markup

Chad

-----Original Message-----
From: Esteve Fernandez [mailto:esteve@sindominio.net] 
Sent: Thursday, November 05, 2009 6:30 PM
To: thrift-dev@incubator.apache.org
Subject: requirements for a new release (was Re: java and twisted python compatibility?)

Hi

> On Thu, Nov 5, 2009 at 2:09 PM, Esteve Fernandez <es...@sindominio.net>
> wrote:
>> I'd be in favor of deprecating the non-framed transports, it's a bit weird
>> that developers have to foresee whether their servers will be accessed by
>> framed or non-framed clients.
>
> +1

Good :-) Given that it's seems reasonable to make the framed transport as the
default one, what do you guys think of marking it as a requirement for
officially support a language and making a new release (which we should do
ASAP)? We're already making some progress towards that, but maybe we should
have a list of what we want to ship.

The list of languages that support framed transports is, so far:

- C++
- Java
- Erlang
- Ruby
- Perl
- Python

support for C# is not committed yet, but Michael gave his approval to this:

http://issues.apache.org/jira/browse/THRIFT-210

Cheers.