subscriber model, general doc question

[Ephraim Dan <E....@F5.com>]

Hi!

We're seriously considering using thrift for an internal application server in our organization.  To this end, I have a couple of questions:

1. One of the things we need is for daemon clients to be able to register for subscriptions to events of certain types, and have the server send events to the client.  The client would presumably have a file-descriptor after subscription/registration, and then poll it for events from the server.  Correct me if I'm wrong but thrift doesn't appear to have out-of-the-box support for this?  Does anyone have recommendations on how this could be achieved without too much effort?

2. Besides #1, thrift *seems* to meet almost all of our needs - except - the docs.  Is anyone actively working on this?

Thanks!

--edan

RE: subscriber model, general doc question

[Ephraim Dan <E....@F5.com>]

Crap - sorry about that - got confused between the lists - should have sent it to thrift-user.
In my defense, it happened because I mistakenly sent a mail to "thrift@publists.facebook.com" which bounced with a message telling me to email thrift-dev, even though it seems to me like it was the equivalent of thrift-user.
Anyway, please ignore.
--edan

-----Original Message-----
From: Ephraim Dan [mailto:E.Dan@f5.com]
Sent: Tuesday, January 06, 2009 16:15
To: thrift-dev@incubator.apache.org
Subject: subscriber model, general doc question

Hi!

We're seriously considering using thrift for an internal application server in our organization.  To this end, I have a couple of questions:

1. One of the things we need is for daemon clients to be able to register for subscriptions to events of certain types, and have the server send events to the client.  The client would presumably have a file-descriptor after subscription/registration, and then poll it for events from the server.  Correct me if I'm wrong but thrift doesn't appear to have out-of-the-box support for this?  Does anyone have recommendations on how this could be achieved without too much effort?

2. Besides #1, thrift *seems* to meet almost all of our needs - except - the docs.  Is anyone actively working on this?

Thanks!

--edan