Hey Craig, I'm assuming you're using C++. There is currently no support for this. The interface between the infrastructure code and the user code is intentially kept narrow to hide the details of the communication code from the application level.
--David On 09/16/2010 12:39 PM, Soules, Craig wrote: > Re-posting hoping someone will see this. > > -----Original Message----- > From: Soules, Craig > Sent: Thursday, September 09, 2010 2:55 PM > To: [email protected] > Subject: Question regarding server-side noticification of server function > exceptions > > Hi all, > > I am trying to determine if there is a way for a server calling > thrift::TProcessor::process() to be notified if there was an exception > during the execution of the underlying RPC call. The reason I ask is > that in some cases, I would prefer that my server drop the client > connection rather than (or in addition to) notifying the client that > there was an error (e.g., in the case of invalid credentials). > > In the version of thrift I branched from some time ago, the process() > call returned a bool, which I thought might be the error notification, > but the auto-generated thrift rpc processing code always returned > true, making this return code somewhat useless. > > In case it isn't clear from above, I am running our own thrift server, > as we needed additional functionality and hooks regarding notification > of client connection and disconnection which could not be achieved > with the basic thrift server. I also was forced to branch due to the > lack of native Windows support in Thrift, so apologies if this has > been changed/fixed in the latest version (although looking at the > source code online, it appears it has not?) > > Thanks, > Craig Soules
