Hi Harrie, I liked the document you wrote about Kannel's API structure. Hope that more of the other developers have a chance to review it. I'll have a deaper look into the patch itself.
IMO, the way apache-1.3 does the modularization may be addopted to Kannel for those API purposes. What do the the others think of this? Should we start re-constructing the current devel tree after we released 1.2.0 and keep a stable branch? I'm +1 for re-constructing a) to a general autoconf layout, hence utilize libtool (yet no assigned volonteers here) b) for modularization using a Kannel API structure (Harrie will be leading this effort, because he's highly involved in Apache's API structure and has most experiences here IMO) BTW, I'm working on a new Kannel web site (using PHP4 and MySQL) and other funny things ;) 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
