2014-11-05 17:49 GMT+01:00 Christopher Burke <christopher.bu...@simulity.com>: > I'm not too sure, I saw the sqlbox as a bit overkill / heavy for my needs. I > guess they're using insert instead of update as they're not updating a > record but adding a new record (I.e. Dlrs mean different things, so an > update is misleading). > > If you want to just store dlr, sqlbox is probably fine, but I still think > it's a bit overkill. I have a nodejs script which is parsing my dlr at over > 2.5k a second, and adding a db shouldn't be more than a few lines but will > probably bring it down lower although I expect it's easier to scale node > than it is to scale kannel > > On 5 Nov 2014 15:11, "Vincenzo Romano" <vincenzo.rom...@notorand.it> wrote: >> >> 2014-11-05 16:01 GMT+01:00 Christopher Burke >> <christopher.bu...@simulity.com>: >> > Yeah, I believe that DLR storage can be achieved using the Kannel SQLBox >> > project. I think GET-URL is possibly less complex. Depends if you’re >> > only >> > storing DLRs or acting on them I guess. >> >> I don't want to write another program when all other bits seems to be >> already there! >> From the source code I can see a set of functions to update the DLR >> storage, one for each different SQL backend. >> But what I see in the reality is that the DLR storage gets only >> INSERTs (upon submission) and DELETEs (upon delivery). >> No UPDATE at all, even if I asked for a dlr-mask=31. >> Isn't there a way to trigger those updates?
In my case, Kannel would act as just a ... SMS gateway. All DLR processing on SMSs would happen through the database. Kannel can scale-up quite easily as you can have multiple instances on multiple network nodes. My RDBMS is PostgreSQL which can also scale-up quite easily. The actual SMS processing would happen through the database.
