Dear lists,

on behalf of the core Kannel developers we wish you all a HAPPY and BLESSED NEW YEAR 2014!

I'd like to take the opportunity to push forward some of the patchsets that have been posted to the devel mailing list, but haven't made it yet into the SVN trunk tree.

Going into the mainline SVN trunk tree should go:

- graceful restarting patchset
- redis support for DLR storage
- smsbox non-blocking HTTP retries

both patches are available and will be committed to the SVN trunk. When done, I would like to go for another Kannel 1.5.1 devel release. Bringing all the latest changes to a release level.

Then having a phase of problem resolution in for the reports that come in, followed by a Kannel 1.6.0 stable release with all the above sets included.

In addition there are several "more" patchsets that need to go into the mainline tree, which are prepared so far:

- abstracted message storage; at the moment the message store-file and spool are pretty bound to the bearerbox incarnation, which we have abstracted the way the DLR storage is abstract, so anyone can more easily implement an own message store here, i.e. using a fast distributed in-memory keystore (redis).

- auto-retry via a list smsc-id patchset; means we can denominate a list of smsc-id's in the msg->sms.smsc_id and in case we get a "not acecpted" by a first smsc-id we automatically retry with the next in the list, etc.

- matchset patchset; the data structure that allows may finer matching definitions for any cases where we use regex values, including support for TRE library which allows fuzzy logic matching inside regex notations.

Comments and thoughts as always welcome.

Cheers,
Stipe

--
-------------------------------------------------------------------
Kölner Landstrasse 419
40589 Düsseldorf, NRW, Germany

tolj.org system architecture      Kannel Software Foundation (KSF)
http://www.tolj.org/              http://www.kannel.org/

mailto:st_{at}_tolj.org           mailto:stolj_{at}_kannel.org
-------------------------------------------------------------------

Reply via email to