Mailing-List: contact dev-help@thrift.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@thrift.apache.org
Received-SPF: pass (athena.apache.org: domain of jrosenblum@conductor.com
 designates 67.192.241.151 as permitted sender)
From: Josh Rosenblum <jrosenblum@conductor.com>
To: "thrift-dev@incubator.apache.org" <thrift-dev@incubator.apache.org>
Date: Wed, 2 Mar 2011 11:03:08 -0600
Subject: Trees in Thrift
Thread-Topic: Trees in Thrift
Thread-Index: AcvY+7S23co/StiER5iGV+1fqbw98A==
Message-ID: <EBB27546-3FEB-4260-A6E4-8300C4EED4B8@conductor.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
	boundary="_000_EBB275463FEB4260A6E48300C4EED4B8conductorcom_"
MIME-Version: 1.0

--_000_EBB275463FEB4260A6E48300C4EED4B8conductorcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

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: h=
ttp://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 / criter=
ia 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 woul=
d be much easier to do this with some sort of recursive datatype. Is someth=
ing like this suitable for thrift, and what would be the best way to satisf=
y this use case if so?

Thanks.

-Josh

--_000_EBB275463FEB4260A6E48300C4EED4B8conductorcom_--