Operation management in the MSC code

Hi, I am going through the SMS code right now and try to convert it to the BSC API and there is something that is quite bad. There are many paths were sending a SMS can end, some do not free the SMS, some not the transaction, some do not remove lock on the channel. I would like to make the radical proposal to solve that. 1.) kill the transaction... 2.) generalize it with the "operation". Right now we do have two operations, one for LU, one for AUTH, we should have them for USSD, SMS and CC as well. Each gsm_subscriber_connection (MSC data) has an operation manager, when a lchan is opened we will attempt to create an operation for the initial message, at the end of one operation the operation manager will check if all operations are completed and then send a clear using the BSC API. The consequence of that is: 1.) we get rid of the refcount and can close channels faster 2.) we will notice... when we run into a timeout and should not... I know this will be a bigger change on the MSC side of things but what do you guys think about it? z.