Trees in Thrift

[Josh Rosenblum <jr...@conductor.com>]

I was reading over the list archives and noticed what seems to be the most-recent discussion there about trees / recursive datatypes in thrift here: http://www.mail-archive.com/thrift-dev@incubator.apache.org/msg06638.html

Wondering whether there has been any further discussion or progress on this. My current use case is trying to send generic query restrictions / criteria to any number of thrift services. I was thinking that sending something like an AST of the criteria expression would be one way to do this. It would be much easier to do this with some sort of recursive datatype. Is something like this suitable for thrift, and what would be the best way to satisfy this use case if so?

Thanks.

-Josh

Re: Trees in Thrift

[Bryan Duxbury <br...@rapleaf.com>]

We aren't planning to support this use case, and I don't think our stance on
this is going to change. It'd be a lot of work to make it happen, and while
it'd be nice, it doesn't seem crucial, and there are perfectly acceptable
workarounds to allow the transmission of things like trees and graphs that
have been discussed on this mailing list in the past.

On Wed, Mar 2, 2011 at 9:03 AM, Josh Rosenblum <jr...@conductor.com>wrote:

> I was reading over the list archives and noticed what seems to be the
> most-recent discussion there about trees / recursive datatypes in thrift
> here:
> http://www.mail-archive.com/thrift-dev@incubator.apache.org/msg06638.html
>
> Wondering whether there has been any further discussion or progress on
> this. My current use case is trying to send generic query restrictions /
> criteria to any number of thrift services. I was thinking that sending
> something like an AST of the criteria expression would be one way to do
> this. It would be much easier to do this with some sort of recursive
> datatype. Is something like this suitable for thrift, and what would be the
> best way to satisfy this use case if so?
>
> Thanks.
>
> -Josh
>