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
