You are right - not a good idea. ok, try this on for size :
- The store mechanism works like before, where each message and ack/nack are first
dumped to storage before doing anything else.
- Messages are not duplicated by the SMSC drivers, but instead the driver just take a
reference to the
What aboud the gw_claim_area_for() call ?
I'm not terribly happy with adding another function call (overhead-wise), but I guess
an optimizing compiler can hack it.
+1 from me if you fix gw_claim_area_for() too :-)
--
Oded Arbel
m-Wise Mobile Solutions
[EMAIL PROTECTED]
Mobile:
