Not an unreasonable suggestion. The client won't even attempt to read the reply, and if the client sends another request after the ONEWAY, it'll get confused by reading back the exception from the 1st call as the result of the 2nd call. Message sequence ids should make it possible to address this issue, though I'm not sure our current implementation does.
So yeah, given that the client will never attempt to read anything back after a ONEWAY, by design, I agree we shouldn't ever send back anything, even in the error state. -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Thursday, March 11, 2010 4:48 PM To: Thrift Developer Subject: Exception after Oneway? If a CALL contains an unknown name, the server returns an EXCEPTION instead of a REPLY. However, what if it is a ONEWAY? Shouldn't it just drop it on the floor without trying to reply? Mayan
