Pedro B. wrote:
... which is a pity. I was recently asked if i was willing to do a migration from another gateway -a fairly good one, also in C, but commercial and not open-source, although they have a trial available for who wants to better know it - i wonder if saying the name here is forbidden ;)
no, this is an open forum, so this is not forbidden.
But with the scenario they painted was something like: there is a .so shared object (they really want to guarantee multi threading) that controls all events occuring in the gateway - connects, reconnects, status messages, MO, MT. Meaning everytime one of these events occur, that same .so is triggered, and from there everything is controlled, from the database tasks (pgsql, with a sh**load of triggers to control the custom mobile marketing campaigns) to the .php that generates the push SI binaries and MMS stuff (nuts, no PPG).
why? Using a PPG for transmitting the MMS notifications is of course "the clean way". But our MMSC has also the ability to push MMS notifications directly via SMS.
Basically this makes more sense, in terms when you really want to control what kind of PDU you want to be transmitted to the phone. In case the PPG has a way of sending the notification PDU that some phones don't like.
In overall, i felt i was not 100% at ease with a migration like this, so i still didn't give them an answer. Of course that if some kind of commercial support was available, i would be a middle man in the migration, but as it is now... tough decision.
The lack in commercial support commitment is not due to "not willing". It's more due to the fact that the business model is to weak (in terms of revenues).
Stipe
mailto:stolj_{at}_wapme.de ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 D�sseldorf, NRW, Germany
phone: +49.211.74845.0 fax: +49.211.74845.299
mailto:info_{at}_wapme-systems.de http://www.wapme-systems.de/ -------------------------------------------------------------------
-----BEGIN PGP PUBLIC KEY BLOCK----- Version: GnuPG v1.2.2 (Cygwin)
mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -----END PGP PUBLIC KEY BLOCK-----
