[ 
https://issues.apache.org/jira/browse/THRIFT-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538473#comment-13538473
 ] 

Roger Meier commented on THRIFT-1801:
-------------------------------------

Fully agree, we need an improved Exception handling and I like to get some more 
contributions from your side. 

We recently got this input here:
THRIFT-1761 Make generated exceptions have a common unique parent
What do you think on this?

Which cross language test suite do you use?
I started this THRIFT-847 ran via test/test.sh

all the best!
roger
;-r

                
> Sync up TApplicationException codes across languages and thrift 
> implementations
> -------------------------------------------------------------------------------
>
>                 Key: THRIFT-1801
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1801
>             Project: Thrift
>          Issue Type: Task
>    Affects Versions: 1.0
>         Environment: all
>            Reporter: Andrew Cox
>            Assignee: Andrew Cox
>             Fix For: 1.0
>
>         Attachments: THRIFT-1801.1.patch
>
>
> Two issues with TApplicationException codes: 
> 1) some languages contained incomplete lists of existing 
> TApplicationException codes
> 2) internally in Facebook thrift servers, we had reserved a few extra error 
> codes for TApplicationException, and those error codes were then claimed here 
> for different uses. this causes conflicts when some clients that know about 
> one set of codes communicates with servers that know about a different set of 
> codes. I've reassigned our internal error code numbers to make space for the 
> ones in more recent thrift code, but to try prevent this from happening 
> again, I'd like to add our own codes to reserve them (these currently won't 
> have any other mention in the thrift libraries right now than being in 
> TApplicationException, but they may eventually be used when we push more of 
> this internal code out).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to