> I like this. These then become separate apps that connect to bearerbox and > provide some form of API into Kannel (http, smpp, emi, xml over > socket....). This way we could even do an Apache mod.
yep. I was also thinking about "connectivity" to Apache. What would be your ideas concerning functionality? What could the module do?
Off the top of my head, so a bit rough and rambly..
When I first started with Kannel over 18months back now. One of my first thoughts was that a lot of what SMSbox does, Kannel already does. So I would see the Apache module using the Apache as the HTTP interface (or gateway as u say), and connecting to bearbox with a persistant connection per Apache child (much like php mysql does). We could use the rewrite functionality to then redirect URIs of a certain form to the bbox connection.
Another idea was to write a PHP module for Kannel that talks to bearerbox.
Apart from msg encoding and concat, smsbox doesnt really do that much. Sure it maps what it gets POST, GET, XML etc to an internal msg and handles the sms-sevice, dlr stuff.
So the main trick would be how / where to handle the sms-service and dlr stuff. Kalle's Netikos does it very nicely in bearerbox. Does it connect back via HTTP to preconfigured Apache rewrite rules and then through to the Apache mod, or should bbox talk directly to the Apache module over its socket connection.
I wonder how many of the Kannel users have built applications in front of Kannel and how many just talk to the smsbox interface straight from there webpage scripting lang?
> yup. but then maybe we should move smsbox into gateway/servers
hmmm, I guess this will be a hard decission. smsbox does what Kannel intends, agregate very specific SMSC protocolls to a very common, HTTP. So I'd vote for leaving this in as the main "gateway" element. Basicailly smsbox is no server, it's a gateway ;)
Well its a gateway to get to the bearerbox functionality that really does the aggregation.
And it is a HTTP server.. We are about to turn our Q, Router, Loadbalancer into a FooBox and it
will have both a HTTP and Socket interface.
So smsbox could be the default --with-server and one could turn it off with --without-server = smsbox
Nisan
> lets keep --with-addon for other loadable modules in the future..
hmm, ok, --with-server is more semantical, yep.
Stipe
[EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG
Vogelsanger Weg 80 40470 D�sseldorf
Tel: +49-211-74845-0 Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de ------------------------------------------------------------------- wapme.net - wherever you are
