Hi Bernino, I'm throwing my 2ct (now to be noted europien Euro Cents :)) on this:
Bernino Lind wrote: > First of all: > The web site: deep links to the various standards, such as the ETSI > standard, with a brief note: "You need this standard in order to do a > ringtone and other binary SMS". The web site is going to be re-designed and include more features. We'll do a state-of-the-art PHP4, MySQL web application out of it :)) > Documentation: more complex examples with source code to sample applications > would be extremely nice. There is already the contrib/ but not especially > well documented - and some of it broken. Extended examples are nice, I agree. We may set up additional documents for certain issues, that go more in detail, i.e. "Using Kannel for WAP", "Uing Kannel for SMS", "Security Considerations", etc. The main problem about this issue is who is going to maintain them?! > There are some things which could be done automatically with some extra > programming inside Kannel. For example, if a programmer wishes to send a > text consisting of more than 160 charecters, then thats only possible if > this programmer knows how to construct the udh, chop the text up and create > the messages. > > Why not do that directly in Kannel ? It shouldnt be too hard. If you mean the automatic splitting of SMS messages (in case of text > 160 chars) to multiple calls, we have this already build in. It may be activated on sms-user basis with the directive "concatanation", see user's guide. > The thing is, this kind of extra functionality is a political decision in a > software project: where to draw the line between end programmer applications > and in-core functionality. Linux for example did not make such a decision, > and suddenly there was a kernel land http server!!! With all the flaws and > exploits that leads to. Yep, that's why we use Apache :)) The line between core functionality and end programmer application level has to defined in some common sence, sometimes it's more sence, sometimes less ;) > Please let me know what you think of these thoughts, also to indicate where > Kannel is going. It's hard to say where Kannel is going. At least I would like to state "Kannel should be the synonym for mobile internet related intrastructure on a open source basis". I would like to see it in the same position as Apache for the HTTP server world. -- that's why I work on both of them :)) Stipe [EMAIL PROTECTED] ------------------------------------------------------------------- Wapme Systems AG Münsterstr. 248 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
