hi,
no problem but then we have at least try to share code with sqlbox and don't
try reinvent the wheel. So the user will have advantage and possibility to
switch between sql smsc module and sqlbox without extra tasks needed.
Because otherwise we duplicate code and that make maintenance not so
-Original Message-
From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf
Of Donald Jackson
Sent: Monday, 14 March, 2011 13:39
To: devel@kannel.org
Subject: [PATCH] Database SMSC driver
Hi everyone,
Here is a new SMSC driver which takes messages and inserts them
Am 18.03.2011 10:06, schrieb Donald Jackson:
Hey Alex,
I think anything is 'possible' but this SMSC was written specifically to make
it easier for users to implement such a scenario. Asking these types of users
to now configure loop backs, a sqlbox and more doesn't make it an easy task
this driver, over using sqlbox?
== Rene
-Original Message-
From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf
Of Donald Jackson
Sent: Monday, 14 March, 2011 13:39
To: devel@kannel.org
Subject: [PATCH] Database SMSC driver
Hi everyone,
Here is a new
Hi everyone,
Here is a new SMSC driver which takes messages and inserts them into a database
table for processing. It also polls (configurable) database tables for MO's and
DLR's if necessary.
This is useful if you have messages incoming over SMPP (or other scenarios I
haven't thought of :D)
What's the advantage of using this driver, over using sqlbox?
== Rene
-Original Message-
From: devel-boun...@kannel.org [mailto:devel-boun...@kannel.org] On Behalf
Of Donald Jackson
Sent: Monday, 14 March, 2011 13:39
To: devel@kannel.org
Subject: [PATCH] Database SMSC driver
Hi everyone
To: devel@kannel.org
Subject: [PATCH] Database SMSC driver
Hi everyone,
Here is a new SMSC driver which takes messages and inserts them into a
database table for processing. It also polls (configurable) database tables
for MO's and DLR's if necessary.
This is useful if you have messages
