You could write such a simple script in any decent web language, and it will perform more or less the same.
Kannel will open many connections to your web server to deliver your messages. The web server will service those connections on multiple threads, instantiating many copies of your script at once. You just have to use proper coding techniques, whatever the language. For example, if you want to write to a log file, you'll have to lock it while you're writing to it. IMHO, for such a trivial task the language of choice won't make much difference. Probably PHP will require less resources than JAVA, but that's a matter of taste, personal opinion, and it depends on the context (if your whole platform is developed in JAVA, unnecesary adding a PHP dependancy would be rather unwise, for example) so don't take my word literally for it. If you need extreme performance (e.g., tens of hundreds of messages per second), you'll have to develop a more scalable approach (maybe inserting into a DB and then retrieve the records from separate box(es) and multiple MTA's). Hope it helps, Alejandro On Fri, Mar 14, 2008 at 1:27 AM, Percy <[EMAIL PROTECTED]> wrote: > > Thxs for the reply. yes..actually i have done that befor using > sms-services > > keyword (defualt). it will capture the sms and call the sms-service > then > > send a email using php script. and also i can send the MSISDN to the > email > > (from address field) reply will call the HTTP request to the gateway > using > > 2 parameters. msg and mobile no.. > > > > but my thought is php is single threaded. one at a time..any comments > on > > that..(gateway will queue the request and send..asynchronous mehtod). > > Well, don't use PHP if you don't see it fits. How many concurrent > connections are you expecting? How many transactions per second are > you going to process? These are only some of the metrics that you > didn't mention in your original post (: > > Anyway, if you're apprehensive with the threading issues, you can opt > for JAVA. Servlets are multithreaded. Servlet containers automatically > creates a new thread for every servlet request it receives. > > When the servlet's done running the the method for the client's > requests, the thread completes and terminates automatically. Servlet > containers does that automatically for you. > > Caveat: this doesn't ensure that you're completely off-the-hook for > thread safety - you can still bump into some synchronization issues. > > Cheers. > >
