RE: kannel 1.2.1 crashes then dlr in use

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]

> I use internal DLR storage everywhere. And I think we must change
<code snipped>

> because i think no differense, in this case, between DLR_BUFFERED and
> DLR_SMSC_SUCCESS. In both cases we must wait for
> DLR_SUCCESS, DLR_FAIL or DLR_SMSC_FAIL. and no need to delete DLR from
> list.
> may be i'm miss.

I have a similar patch which was not accepted into CVS. its still in my CVS as I don't think it does any harm, but I'm far less convinced now that it is needed - you shouldn't store things in the DLR unless you are absolutly sure you can get them later using the same message ID as you generated your self before getting the first response from the SMSC. under most conditions you must hold the message in driver internal storage until you get an ACK, at which time submitting the message to the DLR system so that it will generate you a DLR_SMSC_SUCCESS is redundant : you can do it much faster yourself. on the rare conditions that you have the correct message ID - that will later be used to generate all DLR mesages - before you get an ACK from the SMSC, you can still fake it with driver internal storage, which doesn't really matter for persistancy, as you can't return the message to the bearerbox anyway before you get an ACK - so for sure you still have to keep it in the driver.

--
Oded Arbel
m-Wise mobile solutions
[email protected]

+972-9-9581711 (116)
+972-67-340014

::..
Daughters of feminists love to wear
pink and white short frilly dresses
and talk of successes with boys/
It annoys/
Their Mums ... 
	-- Nancy White