On Fri, 9 Aug 2002, Harrie Hazewinkel wrote: > > Do you have some nifty way to take smsbox down for that use, so that no > > messages are lost while they are being transfered between bearerbox and > > smsbox? (or open http connections) > > (pure speculating here) A way could be to have the smsbox doing some > gracefull restart by reading the configuration while the connections > (sockets) stay connected. Then messages would get queue up. Unless > the restart takes very long you would no loose messages. Not sure how > the timing/speed is for this.
Well my question was not about how it can be done but how they do do it right now :] > > (it is amazing how much it simplifies things to have smsbox in same > > process. And makes Kannel much faster) > > Just curious, but what about the wapbox?? Would that go faster too?? Possibly, but with wap, you do not need to say 'ack' to each message like with smsc > Yes, dynamic configuration is possible via various ways, SNMP, HTTP > or even just some kind of gracefull restart that reads the configuration > and setups the new environment. What I meant here is that dynamic configuration loading inside Kannel without stopping the smsc connections can be done (quite easily), thus effectually same thing as never stopping bearerbox but restarting smsbox > > (for distribution, the possibility to run distinct smsbox could be left, > > too, alhought I do not see much use for that...) > > Only when the load can go so sky high that a singl machine cannot keep up Naturally. But show me the single SMSC connection that can do that. And if you have several SMS center connections, you can have several bearerboxes, too (yes, I know that if you need to reoute things between them, this can still cause problems. That is just what I'm asking here, does anyone really USE that or is it just speculation that it CAN be done and used? Is it worth all the pain of message/ack/dlr transfer between smsbox and bearerbox?) Usually the speed of applications (oh, the java servlets) and SMSC connections is the only factor of the speed. The core Kannel can handle like 1000-2000 msg/s of fixed answers in normal modern tabletop, like 500-1000 HTTP based services (if the server is fast enough) SMS centers usually do something between 10-50/s, java servlets less. Correct me if I'm horribly wrong -- &kalle marjola product concept manager NETikos finland (http://www.netikos.fi)
