Re: [PATCH] Sending catenated messages in incorrect order

Hi Stipe,

Stipe Tolj wrote:
> Alexander Malysh wrote:
> 
>> Hi,
>>
>> sorry but it seems we make workarounds for buggy SMSC. I'm -1 for this 
>> patch. They must fix SMSC instead of adding some workarounds where 
>> those  don't belong to. Priority has _nothing_ todo with receiver and 
>> udh. Instead SMSC devels should read spec properly (EMI 4.0, GSM 
>> 03.38, GSM 03.40). There is not sign of catenated msgs ordering.
> 
> yep, agree'ing here to Alex's position. Mainly this was because of my +0 
> voting.  Actually it may be more -0 ;)
> 
> @Enver: can you please check what vendor this specific EMI SMSC is? If 
> it is a non standard vendor, hence, home-brewed, then you should force 
> them to obey the specs.
> 
> We really don't want to add workarrounds for bugs of other people's 
> software, that's why specs are for.

The SMSC is actually a home-brewed proxy in front of the real SMSC which 
is there solely for billing purposes.

I fully agree with the "avoiding workarounds" concept. With the patch, I 
was trying to point out a problem which happens in rare circumstances.

My initial point was to post a quick and dirty solution, hopefully get 
some constructive comments on it (thankfully that usually does happen) 
and later on fix the patch to the de-jure solution.

Thanks,
-- 
Enver